> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/technical-documentation/crobox-mcp.md).
# Crobox MCP
The Crobox MCP connects your AI assistant to Crobox, letting you ask plain-language questions about experiences, analytics, product data, and website integration, and draft changes for team review.
MCP stands for Model Context Protocol, an open standard that lets AI assistants such as Claude work with other software securely. The Crobox MCP is available on all Crobox plans.
## Get started
1. **Check your AI assistant is compatible.** The Crobox MCP works with ChatGPT, Claude, and Claude Code. See [Connect an AI assistant](#connect-an-ai-assistant).
2. **Connect it to Crobox.** Add `https://app.crobox.com/api/mcp` as a connector in your AI assistant, log in to Crobox, and select **Allow access**. See [Connect an AI assistant](#connect-an-ai-assistant).
3. **Review proposals in Crobox.** When your assistant drafts a change, it appears in the notification bell in Crobox as **Change proposal · review**. Open it, check what will change, and apply or reject it. See [Review and apply change proposals](#review-and-apply-change-proposals).
## Connect an AI assistant
The Crobox MCP currently works with ChatGPT, Claude, and Claude Code.
Claude.ai
Connecting takes a couple of minutes. You need a Crobox login with access to at least one container, and the Crobox MCP server URL: `https://app.crobox.com/api/mcp`
**Connect Claude**
1. Open and log in to Claude.
2. Go to **Settings › Connectors**.
3. Select **Add custom connector**.
4. Enter a name, such as "Crobox", and the server URL `https://app.crobox.com/api/mcp`.
5. Select **Connect**. Claude opens the Crobox login page.
6. Log in to Crobox. On the **Authorize** screen, select **Allow access**.
7. In a new conversation, make sure the Crobox connector is switched on.
{% hint style="info" %}
On Claude Team and Enterprise plans, an owner may need to add the Crobox connector for your organization before you can connect it.
{% endhint %}
Claude Code
**Connect Claude Code**
1. In your terminal, run:
```bash
claude mcp add crobox --transport http https://app.crobox.com/api/mcp
```
2. Start Claude Code by running `claude`.
3. Run `/mcp`, select **crobox**, and select **Authenticate**.
4. Log in to Crobox in the browser window that opens and approve access.
ChatGPT
**Connect ChatGPT**
1. Open ChatGPT and select **Plugins**.
2. Select **Add** then **Add custom MCP server**.
3. Name the server "Crobox" and add the server URL: `https://app.crobox.com/api/mcp`.
4. Add the server, then log in to Crobox and approve access.
5. You can now @Crobox or just chat with your agent to get started.
### Approve access
After you log in, Crobox shows an **Authorize** screen naming your AI assistant. It explains that the assistant will act as you and can only see the data your account already has access to, and lists what it's asking for:
* Confirm your identity
* Read your name and profile details
* Read your email address
* Stay connected when you are not using the app
* Draft configuration changes for you to review in Crobox. Nothing changes until you apply it.
Select **Allow access** to finish connecting, or **Cancel** to stop.
The last permission only appears if your AI assistant asks for it. Without it, your assistant can still read your Crobox data, but it can't draft proposals, upload images, create preview links, or run test Sagent conversations.
{% hint style="success" %}
You're connected.
{% endhint %}
{% hint style="info" %}
In your AI assistant's list of tools, Sagent appears as "Product Chat". Both names refer to the same experience.
{% endhint %}
## Review and apply change proposals
Your assistant never changes Crobox directly. When you ask for a change, it drafts a change proposal, and a person on your team decides whether to apply it.
### Find the proposal
When a proposal is drafted, everyone who can apply it (Editors, Publishers, and Admins) gets a notification. Open the notification bell in Crobox and select **Change proposal · review**. The proposal opens in a side panel on the page of the first experience or setting it changes.
{% hint style="info" %}
There's no separate list of all proposals. You open each one from its notification or from the link your assistant shares.
{% endhint %}
### Review what will change
Each proposal shows:
* **Title** summarizing the change
* **Attribution**, for example "Drafted by claude.ai for Marie", with the date and expiry date
* **Rationale** explaining why your assistant suggests the change
* **Every change** with its location, the current value (struck through), and the new value
If something doesn't look right, reject the proposal and ask your assistant for a revised one.
### Apply or reject
Select **Apply** to make the change, or **Reject** to close the proposal without changing anything. Any Editor, Publisher, or Admin can apply or reject a proposal, not only the person who requested it. The change is made under the name of the person who applies it.
{% hint style="warning" %}
If a proposal changes code or styling, you need developer mode in Crobox to apply it. Ask an admin to approve developer mode for your account.
{% endhint %}
### What happens after you apply
The Crobox MCP never publishes anything. Most changes become a draft that you publish in Crobox when you're ready, but some go live as soon as they're applied.
| Change | After you apply |
| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Product Finder (new or changed) | Saved as a draft. Publish it in Crobox. |
| Campaign (new or changed) | Saved as a draft. Publish it in Crobox. |
| Sagent (new or changed) | Saved as a draft. Publish it in Crobox. |
| Product Recommender | Saved as a draft. Publish it in Crobox. |
| Comparison Tool | Saved as a draft. Publish it in Crobox. |
| Builder and finder components | Saved as a draft. Goes live with your next website integration publish in **Settings › Versions**. |
| Website integration (triggers, placeholders, actions, packages) | Saved as a draft. Goes live with your next publish in **Settings › Versions**. |
| Product properties (new or changed) | **Live immediately** |
| Product feed mappings and CSV settings | **Live immediately**, used from the next feed run |
| Sagent feed export columns | **Live immediately** |
Crobox labels these changes "Goes live immediately" in the proposal panel, so you always know before you apply.
{% hint style="info" %}
Applied proposals don't appear as separate entries in **Settings › Versions**. Website integration and component changes show up in your next version as regular edits by the person who applied them.
{% endhint %}
### When a proposal can't be applied
**Something changed since the proposal was drafted.**\
Crobox checks that every current value still matches the "before" value in the proposal. If anything has changed, for example a colleague edited the same question, nothing is applied and the proposal stays open. Ask your assistant for a fresh proposal.
**The proposal has expired.**\
Proposals expire seven days after they're drafted. After that, the **Apply** and **Reject** buttons are disabled. Ask your assistant to draft it again.
**Only part of the proposal was applied.**\
If an error occurs partway through, Crobox shows the result for each change, so you can see exactly what was applied. Ask your assistant to propose the remaining changes.
## What you can do with the Crobox MCP
**Understand performance.** Ask how a campaign is performing against its control, which Product Finder answers lead to the most conversions, or how Sagent conversations are trending over the last month.
**Check your setup.** Have your assistant review your website integration health, look for client-side errors, or check whether your product data is complete and up to date.
**Explore your catalog.** Search products, look up property values, preview which products a Product Finder recommends for a given set of answers, or inspect a feed's configuration.
**Draft changes.** Ask your assistant to adjust a Product Finder question, update campaign messaging, tune a Product Recommender, or fix a placeholder selector.
A few tools act straight away without a proposal: uploading images, creating preview links, and running test Sagent conversations. None of these change what your shoppers see. For every tool, with example prompts and limits, see the [Crobox MCP tool reference](/technical-documentation/crobox-mcp/crobox-mcp-tool-reference.md).
## What the Crobox MCP can access
The Crobox MCP connects as you. It uses your Crobox login and your existing role, so your assistant can only see and do what you can. Your role in a Crobox organization applies to all of that organization's containers.
| Your role | What you can do with the Crobox MCP |
| --------------------------- | --------------------------------------------------------------------------------------- |
| Viewer | Read experiences, analytics, product data, and website integration, and draft proposals |
| Editor, Publisher, or Admin | Everything above. You can also apply or reject proposals in Crobox. |
| No role in the organization | Nothing. Its containers aren't visible to your assistant. |
If you have access to more than one container, mention the container in your question, or ask your assistant to list the containers you can access first.
## Data and privacy
* Your questions and your assistant's answers stay in your AI assistant. Crobox doesn't keep a record of what you ask.
* Crobox data your assistant reads is passed to your AI assistant to answer your question. Your AI provider's terms and data policies apply to that data.
* Crobox stores the proposals your assistant drafts, including your name and the AI assistant that drafted them, so your team can review them.
* Test Sagent conversations are stored as preview conversations and kept out of your Sagent reports and analytics by default.
## What the Crobox MCP can't do
* Publish versions, experiences, or website integration changes
* Delete or archive experiences, files, or other configuration
* Manage users, roles, or organization settings
* Change a feed's source or credentials
* Change Sagent's tools, knowledge settings, or AI model
* Apply its own proposals
## Troubleshooting
My assistant shows no Crobox tools
Remove the Crobox connector in your AI assistant, add it again, and log in to Crobox. In Claude, do this under **Settings › Connectors,** in ChatGPT do this in **Plugins**.
My assistant can read data but can't draft changes
Your AI assistant didn't ask for permission to draft changes when you connected. Check its settings for the Crobox connection, or contact Crobox support.
My assistant can't see a container I expected
Ask your assistant "Which Crobox containers can you see?" If the container is missing, your Crobox login doesn't have access to it. Check your access in Crobox, or ask your Crobox admin.
I'm connected with the wrong Crobox login
Remove the Crobox connector in your AI assistant, connect again, and log in with the right account.
My AI tool can't connect
The Crobox MCP currently works with ChatGPT, Claude, and Claude Code. If you use another AI assistant, follow the similar steps to connect the custom MCP server, or contact your Customer Success Manager for help. If you see an "Unsupported protocol version" error, update your AI assistant and try again.
## Frequently asked questions
Does applying a proposal publish my changes?
No. The Crobox MCP never publishes. Most changes become drafts you publish yourself. The exceptions are product properties, product feeds, and Sagent feed export columns, which go live as soon as you apply.
Does my assistant get more access than I have?
No. Your assistant works as you, with your existing Crobox role. If your access is removed or your account is deactivated, your assistant loses access on its very next request.
Can a Viewer create proposals?
Yes. Viewers can ask their assistant to draft a proposal, but only an Editor, Publisher, or Admin can apply it.
Does a new proposal replace an older one for the same change?
No. Each proposal is independent. If your assistant drafts a revised version, reject the older one so your team doesn't apply both.
Can I edit a proposal before applying it?
No. Reject it and ask your assistant for a revised version, or apply it and make further edits in Crobox.
Can admins turn off the Crobox MCP or make it read-only for our organization?
Not currently. Access is controlled through each person's Crobox role, and every change still needs an Editor, Publisher, or Admin to apply it in Crobox.
Do I need a client ID or client secret?
No. Claude and Claude Code handle this automatically when you connect. Tools that require you to enter a client ID and secret can't currently connect.
Can colleagues see what I ask my assistant?
No. Your conversations stay in your AI assistant. Colleagues only see proposals your assistant drafts for you, which carry your name.
Does it work with single sign-on?
Yes. You log in to Crobox the same way you normally do, including single sign-on and two-factor authentication.
Is there an API key for scripts or automations?
No. The Crobox MCP always connects as an individual Crobox user through a login. There is no API key or service account option.
Does the Crobox MCP cost extra?
No. It is included on all Crobox plans.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.crobox.com/technical-documentation/crobox-mcp.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.