Skip to main content
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 that power Chats. MCP (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.

​
Connecting

The server is available at: 
https://mcp.conversion.ai/mcp
Add this URL as a remote MCP server in your client. On first connect, you’ll be redirected to sign in to Conversion and authorize access. The connection is scoped to a single business (the one tied to your account) and a single user, and grants the client access to that business’s data. 
{
  "mcpServers": {
    "conversion": {
      "url": "https://mcp.conversion.ai/mcp"
    }
  }
}
For clients with a connector UI (such as Claude), add a custom connector, paste the URL above, and complete the sign-in prompt.
Access is authorized through your Conversion account using OAuth. You don’t manage a separate API key for the MCP server. Signing in handles authentication.

​
What it can do

The MCP server exposes the same read and build actions Conversion AI uses in chat. See Tool calls for the full descriptions.
AreaActions
ContactsList, get, count, read events and automation runs, list and create fields, import from CSV.
AudiencesList, create, update, rename, add contacts.
EmailsList, get, read metrics and recipients, create blasts, rename.
FormsList, get, read submissions, rename.
WorkflowsList, get, read runs and metrics, rename.
CampaignsList, create, rename, duplicate, manage members, types, and tokens.
FoldersList, create, move assets, rename.
WorkspaceRead email settings and logo.
SyncList sync batches and logs.
ArtifactsCreate, update, and apply email, form, and workflow artifacts.

​
What it can’t do

The MCP server exposes a narrower surface than Chats. It does not include:
Not availableNotes
Sandbox and file toolsRunning code, reading and writing files, and uploading images are only available in chat, where the sandbox runs.
It also keeps every limitation that applies to Conversion AI generally. It cannot delete anything, and it cannot edit existing workflows.

​
Artifacts and confirmation

Building an email, form, or workflow over MCP works the same way as in chat: the AI client creates an artifact, and nothing changes in your workspace until that artifact is applied with the apply action. Conversion’s in-chat Allow / Deny approval prompts are part of the chat interface and don’t appear over MCP. Instead, each tool tells your AI client whether it only reads data or whether it writes, and your client decides when to ask you to confirm. Confirmation behavior depends on the client you connect.
Because confirmation is handled by your AI client rather than Conversion, review your client’s settings so you understand when it will ask before taking a write action on your workspace.