> ## Documentation Index > Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Connect external AI tools to your Conversion workspace through the Model Context Protocol. The Conversion MCP server lets external AI tools like Claude, ChatGPT, and Cursor work with your Conversion workspace directly. Once connected, those tools can look up your data and build marketing assets using the same [tool calls](/product-docs/conversion-ai/tool-calls) that power [Conversion AI](/product-docs/conversion-ai/introduction) in chat. [MCP](https://modelcontextprotocol.io) (the Model Context Protocol) is an open standard for connecting AI applications to external systems. The Conversion MCP server is a remote server you add to any MCP-compatible client. It's the second way to use Conversion AI: instead of the in-product [Chats](/product-docs/conversion-ai/introduction) interface, you bring your own AI client. You can add Conversion to any MCP-compatible client. In ChatGPT, Conversion is available as an app: search for it in the app directory and connect in a couple of clicks. In Claude and other clients, add it by server URL (Conversion is **coming soon** to Claude's connector directory): ``` https://mcp.conversion.ai/mcp ``` See [Connecting](/product-docs/mcp/connecting) for client-specific steps. ## Same engine, different surface Chats and the MCP server run on the same underlying tools against the same workspace data. What changes is where the conversation happens, what context Conversion provides, and how a few things behave once you're connected: | | Chats | MCP server | | -------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | Where it runs | Inside Conversion, on any page | Your own AI client (Claude, ChatGPT, Cursor, …) | | Who drives the model | Conversion | Your client | | Reading and lookups | Same tools | Same tools | | Creating new assets | Staged as [artifacts](/product-docs/conversion-ai/artifacts) you review and apply | [Direct create tools](/product-docs/mcp/differences#creating-new-assets), live but dormant | | Editing existing assets | [Artifacts](/product-docs/conversion-ai/artifacts) and in-product [approvals](/product-docs/conversion-ai/approvals) | [Raw, immediate edit tools](/product-docs/mcp/differences#editing-existing-assets) | | Confirmation before writes | In-product [Allow / Deny](/product-docs/conversion-ai/approvals) | Handled by your client | | Business context | [Universal Business Context](/product-docs/mcp/differences#universal-business-context) applied automatically | Not provided; your client is the model | | Files and sandbox | Available | Not available | See [Differences from chat](/product-docs/mcp/differences) for the full comparison. ## Scope of a connection Each connection is scoped to **a single business and a single user**: * You sign in with your Conversion account and authorize **one** of your businesses. * The client can only see and act on data in that business, and only within **your** role and permissions there. * To work with a different business, you connect again and authorize that one. See [Connecting](/product-docs/mcp/connecting) for the setup and authentication details. ## Next steps Add the server to your client, sign in, and choose a business. Everything the MCP server can read, create, and edit. What's the same as Chats, and what works differently. How Conversion AI works in the in-product chat.