> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/features/use-maker-from-your-ai-assistant.md).
# Use Maker from your AI Assistant
***
### Key Benefits
* **Talk to Maker from Claude, ChatGPT, Claude Code, or Codex**
* **Your AI subscription does the thinking.** No Maker credits used for the assistant's work itself. Generation runs on your existing Claude Pro, ChatGPT Plus, or Cursor plan.
* **Your assistant can list, open, edit, and publish your Maker projects** including the things only Maker can do (preview, hosting, A/B tests, variants, your skill catalog).
* **One-time setup.** Connect once and Maker shows up in every new chat with that assistant.
***
### Supported AI Tools
* Claude Desktop & Claude.ai
* OpenAI Codex
* ChatGPT
* Claude Code
***
### How to Set It Up
Open **Settings > AI assistants** in Maker. You'll see a card for each assistant we support. Pick the one you use, follow the four-step pop-up, and you're done.
#### Claude Desktop & Claude.ai
Works in both the web app at **claude.ai** and the Claude desktop app.
1. **Pro plan:** Open **Customize > Connectors** in Claude and click **+ Add custom connector**.
2. **Team or Enterprise:** Your admin opens **Organization settings > Connectors > Add > Custom > Web** once for the whole org. After that, you go to **Customize > Connectors > Connect**.
3. Paste the Maker server URL (it's shown in the popup) and click **Add**, then **Connect**.
4. Sign in to Maker in the popup that opens. Claude will then have Maker's tools available in any conversation.
> Once connected, you can pin Maker tools on or off per chat using the **Tools** button in Claude's composer.
#### ChatGPT
Available on **Business, Enterprise, and Edu** workspaces with developer mode turned on.
1. Open ChatGPT and go to **Settings > Connectors**.
2. Click **Add connector** and paste the Maker server URL from the Maker popup.
3. Complete the sign-in flow. Maker tools then appear in the composer's **Tools** picker.
#### Claude Code (for developers on your team)
Anthropic's terminal coding agent. One command and you're done.
1. Run this in a terminal:
```
claude mcp add --transport http maker https://ai.maker.co/mcp
```
2. Start or restart a Claude Code session, then type `/mcp` and follow the sign-in prompt.
3. Ask Claude Code "list my Maker projects" to confirm it worked.
#### Codex (for developers on your team)
OpenAI's terminal coding agent. Set up via CLI or by editing your config file.
1. Run this in a terminal:
```
codex mcp add maker --url https://ai.maker.co/mcp
```
2. Run `codex mcp login maker` to sign in.
3. Or edit `~/.codex/config.toml` directly with the snippet shown in the Maker popup.
***
### How It Works
When you connect an AI assistant to Maker, you're plugging it into the same set of tools you use inside the Maker app—opening projects, editing copy, swapping images, kicking off A/B tests, pulling from your skill catalog, looking at insights, and so on.
The assistant runs in its own window (Claude, ChatGPT, etc.) and calls Maker behind the scenes whenever your request needs Maker to do something.
**Your AI subscription does the thinking.** All the language model work—understanding your prompt, drafting copy, deciding which tool to call—happens inside the assistant you already pay for. Maker doesn't bill a token for any of it. If you're already paying for Claude or ChatGPT, you've already paid for half of Maker.
**Plus everything only Maker can do.** A chat window on its own can't host your site, preview it across viewports, run a real A/B test, or push to your custom domain. Your assistant calls Maker for those steps. The chat sees the result and keeps going.
Anything you can do by clicking around in Maker, your assistant can now do for you from a chat.
***
### What You Can Ask Your Assistant to Do
Some prompts that work right out of the box:
* "List my Maker projects from the last two weeks."
* "Open the coffee-shop landing page and rewrite the hero headline."
* "Take a screenshot of my pricing page preview."
* "Make three colour variations of this landing page."
* "Update the testimonial section to match my brand."
* "Why isn't the contact form submitting?"
* "Spin up an A/B test of two different hero photos on the home page."
You don't need to memorise commands—talk to the assistant the way you normally would. It figures out which Maker tool to call.
> **The fastest way to learn what's possible is to ask the assistant itself.** Right after you connect, try "What can you do with Maker?" or "What Maker tools do you have available?"—the assistant has the full, up-to-date list of every Maker capability it can reach, and it'll tell you in plain English. We add new tools regularly, so the assistant's answer is always more current than any list we could write here.
***
### Managing Your Connections
Open **Settings > AI assistants** and scroll to **Server details** to see:
* The Maker server URL you'd paste into a new client.
* The list of assistants currently connected to your account, with the last time each one was used.
* A **Revoke** button on each—click it to disconnect that assistant. The next time you ask Maker to do something from that chat, you'll be asked to sign in again.
***
### Tips & Best Practices
* **One connection covers every org you belong to.** The assistant defaults to the org you picked when you signed in, but it can hop between any of your other orgs mid-chat—just ask, e.g. "which Maker orgs am I in?" and then "switch to the marketing team org". The switch lasts for the rest of that session.
* **You can have more than one assistant connected at the same time.** Use Claude for design work and ChatGPT for ops if that's how your brain works.
* **Open the live preview side-by-side with your chat.** Pop your project's preview URL into a second window next to Claude (or on a second monitor). Every time your assistant edits the project, the preview refreshes automatically—you'll see the change land while you're still talking to the chat.
* **Pair it with Comments.** Open the preview, leave Comments on every spot you want changed, then ask your assistant "implement everything in my open Comments on this project". The assistant works through them one by one and you stay in the visual world the whole time.
* **You can still grab the visual editor for finishing touches.** Some things are faster by hand—nudging a margin, picking a colour, swapping a single image. Switch to the Maker preview, make the small tweak in the visual editor, then go back to the chat for the next big move. Best of both worlds.
***
### Plan & Pricing
The AI-assistants connection is available on the **Max** plan and above. On lower tiers you'll still see the setup page, but the connector cards open an upgrade prompt instead of installing.
Generation runs on your AI assistant's own subscription—Maker credits are not spent on the assistant's thinking, drafting, or tool-calling itself.
**Two exceptions** can still cost Maker credits: **image generation** and **video generation**. These run on Maker because they're not something a chat window can do alone. Whenever your assistant is about to call one of those tools, it shows you the exact credit cost first and asks you to confirm—nothing kicks off until you say yes.
***
### FAQ
Does this use my Maker credits?
Not for the assistant's thinking, drafting, or tool-calling—all of that runs on your Claude Pro / ChatGPT Plus / Cursor subscription.
Image generation and video generation still cost Maker credits because those don't run in the chat—they run on Maker. Your assistant always shows you the exact credit price first and waits for you to confirm before kicking either one off, so nothing surprises you.
Which plan do I need?
The connection is available on the **Max** plan and above. Free, Pro, and Teams users can see the setup page and learn about the feature, but installing a connector requires Max. If your organization downgrades out of Max, any existing connections stop working until you upgrade again.
Is this secure?
Yes. The connection uses standard OAuth sign-in—Maker never sees your AI assistant's password, and your assistant never sees a Maker API key. Every request your assistant makes is scoped to your account and to the specific tools you've granted. You can revoke a connection at any time from **Settings > AI assistants > Server details**.
What is MCP? I've seen the term in my assistant's settings.
MCP stands for Model Context Protocol—an open standard for letting AI assistants talk to outside tools and apps. Claude, ChatGPT, Codex, and Claude Code all support it, which is why the same Maker connection works in all of them. You don't need to learn anything about it to use Maker from your assistant; it's just the plumbing underneath.
What can my assistant actually do once it's connected?
Roughly anything you can do by clicking around inside Maker: list and open projects, edit copy, swap images, generate new sections, screenshot the preview, push changes live, set up A/B tests, create variants, pull from your skill catalog, and read your project insights. If a teammate adds a new skill to your catalog, your assistant can use it the next time you chat—no extra setup needed.
The single best way to get the definitive list is to ask the assistant itself: "What can you do with Maker?" It sees the full toolkit (which we keep adding to), and its answer will always be more current than this page.
Can I limit what my assistant can do?
Yes, in two places. Inside the assistant (Claude, ChatGPT), you can toggle Maker tools on and off per conversation using the **Tools** picker—useful when you want a chat to only talk about ideas, not actually publish anything. Inside Maker, organization admins control who has the **Max** plan access in the first place; viewers and members without write access still can't push changes through Maker, no matter what they ask the assistant to do.
How do I disconnect an assistant?
Open **Settings > AI assistants > Server details**. Each connected assistant has a **Revoke** button—click it and that assistant loses access immediately. To reconnect later, follow the same setup steps again.
Why is the AI-assistants tab showing a "MAX" badge for me?
Your organization isn't on the Max plan, so the connection itself is locked. You can still browse the setup page and see what the feature does—but clicking a connector card will prompt you to upgrade. Max-plan organizations see a "NEW" badge instead.
Can my whole team share one connection?
No—each teammate sets up their own connection to their own AI assistant. That way every chat runs against the right person's identity inside Maker, and revoking your access doesn't affect anyone else.
Does it work with Cursor / Cline / another AI tool I use?
Most modern AI assistants support custom connectors, so chances are yes. Try pasting the Maker server URL (from **Settings > AI assistants > Server details**) into your tool's connector or integration screen. The setup steps in Maker cover the four assistants we've tested end-to-end; others usually follow the same pattern.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.maker.co/features/use-maker-from-your-ai-assistant.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.