> ## Documentation Index > Fetch the complete documentation index at: https://docs.promptjuggler.com/llms.txt > Use this file to discover all available pages before exploring further. # Build with your AI assistant > Connect Claude, ChatGPT, Claude Code, Codex or any MCP client to PromptJuggler, and build your prompts, workflows and evaluations together. AI can build your AI. Whether you’re shaping a feature or tuning a prompt, your assistant can create prompts, workflows and evaluations in PromptJuggler, run them, and improve them with you. It connects through [MCP](https://modelcontextprotocol.io/), the open standard for plugging AI assistants into the tools you use. Connect it once, then ask in your own words: * “Draft a prompt that sorts support tickets by urgency, try it on these three tickets, and show me the results.” * “Compare v3 and v4 of the summariser on these inputs and tell me which handles the edge cases better.” * “Build a workflow that drafts a reply and has a second prompt check its tone before returning it.” * “Find yesterday’s failed runs of the triage workflow and tell me what went wrong.” * “What can you do in PromptJuggler?” ## Connect over MCP PromptJuggler’s MCP server has one address for every assistant: `https://mcp.promptjuggler.com`. **Working in more than one workspace?** Each has its own address, which **Connected apps** on My Account lists for you to copy. Add one connection per workspace with its address, and name each connection after its workspace. > [tab] Claude > > On claude.ai or in the Claude desktop app: > > 1. Go to [Customize > Connectors](https://claude.ai/customize/connectors). > 2. Click **Add**, then **Add custom connector**. > 3. Name it PromptJuggler, enter `https://mcp.promptjuggler.com` as the server URL, and click **Continue**. > 4. Keep the settings Claude detects, and click **Add**. > 5. Click **Connect**. > > On a Team or Enterprise plan, an Owner adds the connector once under **Organization settings > Connectors**. You then find it under **Customize > Connectors** and click **Connect**. > > Sign in, pick the workspace, and choose what your assistant may do. > [tab] ChatGPT > > Add it once, then bring it into any chat by typing `@` and picking PromptJuggler. > > 1. Open [Plugins](https://chatgpt.com/plugins) on chatgpt.com. In the ChatGPT desktop app, click the **Plugins** icon in the left pane. > 2. Click **Add** at the top right, then **Add custom MCP server**. > 3. Name it PromptJuggler and enter `https://mcp.promptjuggler.com` as the **Server URL**. > 4. Under authentication, pick **OAuth**. > 5. Click **I understand and want to continue**, then **Create as a plugin**. > 6. Install the plugin. > > If you use ChatGPT in a company workspace, your admin may need to allow it first. > > Sign in, pick the workspace, and choose what your assistant may do. > [tab] Claude Code > > **Already connected Claude?** If you sign in to Claude Code with your Claude account, it has every connector you added in Claude, PromptJuggler included, in the terminal, your IDE and the desktop app’s Code tab alike. Type `/mcp` to see it. > > **In the terminal or your IDE**, you can also add it on its own: > > ```bash theme={null} > claude mcp add --transport http --scope user promptjuggler https://mcp.promptjuggler.com > ``` > > Then type `/mcp` in Claude Code and select **promptjuggler** to open the sign-in page in your browser. > > **In the Claude desktop app’s Code tab**, add PromptJuggler as a connector the way the Claude tab shows; the Code tab picks it up. > > Sign in, pick the workspace, and choose what your assistant may do. > [tab] Codex > > **In the terminal** (Codex CLI), run: > > ```bash theme={null} > codex mcp add promptjuggler --url https://mcp.promptjuggler.com > codex mcp login promptjuggler > ``` > > **In the ChatGPT desktop app or your IDE** (Codex), open **MCP servers** in the Codex settings and click **Add server**. Choose **Streamable HTTP**, enter the address above, save, and select **Restart**, then **Authenticate**. > > The terminal and the apps share this setup, so adding PromptJuggler in one is enough. > > Sign in, pick the workspace, and choose what your assistant may do. > [tab] Other apps > > Any other MCP client connects one of two ways. > > **If it signs in with OAuth**, add the server `https://mcp.promptjuggler.com`, then sign in, pick the workspace, and choose what your assistant may do. > > **If it takes a token instead**, create one: > > 1. In PromptJuggler, click **Account** at the bottom of the sidebar. > 2. Under **Connected apps**, click **Create token**, then pick the workspace, what your assistant may do, and when the token expires. > 3. Copy the token. It’s shown only once. > 4. In your app, add the server `https://mcp.promptjuggler.com` with the header `Authorization: Bearer `. ## You stay in control * **You choose what it can reach.** Each connection works in the one workspace you pick, and you decide whether your assistant may edit drafts, start runs and publish. * **It asks before publishing.** Publishing can change what your product runs, so your assistant checks with you first. * **You can disconnect it any time.** **Connected apps** on My Account lists your assistants and tokens, so you can disconnect an assistant or revoke a token whenever you like. ## From idea to product Your assistant works with the same drafts, versions and tags you do. [Naming & Versioning](https://docs.promptjuggler.com/concepts/naming-and-versioning.md) explains them; here’s how they take an idea all the way to your product. **Publish once it works.** Drafts are yours alone, so you and your assistant can iterate freely. Publishing makes a version your team and your product can use. **Choose how your product picks up changes.** Your product can call a version number, so changes ship with your own releases. Or it can call a tag such as `production`, so changes ship, and roll back, without a deploy. Both work well. A common setup pairs a `staging` and a `production` tag with [matching environments](https://docs.promptjuggler.com/guides/integration.md#environment-matching), so each gets its own variables and webhooks. **Wire it in.** Ask Claude Code or Codex to [call it from your code](https://docs.promptjuggler.com/guides/integration.md), or ask your assistant for a handover note for your developers. Every step is one request away: > Publish this as “shorter answers” and run the ticket evaluation on it and on the version in production. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.