Skip to main content
MCP shares product tools with Conversion AI in chat and uses separate direct tools for editing existing assets. Tools behind workspace feature flags are hidden unless those features are enabled. Every call is still subject to your backend permissions. The server refreshes feature availability on each request, including calls to a tool your client discovered earlier. If workspace flags cannot be read, gated tools stay hidden. Conversion chat’s disabled and approval-required tool settings do not control MCP; configure approvals in your MCP client.
An available write tool applies its change when your client calls it. Configure your client’s approval settings to control when it asks for confirmation. Conversion does not show its chat approval dialog for MCP calls.

Reading and lookups

Use search to find records by name or meaning. Each kind of record has its own list tool with structured filters and pagination, such as contact_list, form_list, file_list, or media_list. Only the list tools available to you appear. Custom objects, reporting, landing pages, Plays, queues, and Airtable setup use the same workspace feature gates as chat. A feature being enabled does not override your backend permissions.

Creating and editing

New emails, forms, landing pages, and workflows are created as drafts. Sending a blast, publishing a form or landing page, or activating a workflow remains a separate action in Conversion. Landing page tools can also list, add, verify, and remove a page’s custom-domain addresses and switch it between public and password-protected. They never set a page’s password; a person sets it in Conversion. Requiring a password on a page that has none leaves it closed to visitors until someone sets one. In Conversion chat these address and access changes ask for approval by default; over MCP, your client’s approval settings apply. For existing assets, use MCP’s direct update tools: These tools write directly when the MCP client calls them, after any confirmation configured in that client. They do not use Conversion chat’s pending-edit or approval flow. Read the current asset before editing. Complete email bodies, form designs, and landing page designs replace the existing definition; omitted components are removed. Template edits and replacement of an existing workflow’s graph are unavailable over MCP. Use Conversion for those changes.

Deletes and external actions

Each kind of record has its own delete tool, such as contact_delete, delete_email, or delete_landing_page, so your client can approve each one separately. Folders and campaigns must be empty first; a refused delete explains what is in the way. Deletes, provider linking, and Salesforce linking or sync are available over MCP, subject to backend permissions and feature gates. Read tool descriptions carefully: these actions can remove data or change connected services. The campaign_add_members and campaign_update_member_status tools still refuse the Registered webinar status because it can register and email a person through the webinar provider. The guard reads the status and refuses the change if it cannot resolve it. Play management can activate a Play only when the workspace feature and activation permissions permit it. Queue reads are available under the queue feature gate. Over MCP, queue_decide_item supports cancellation only; placing, rescheduling, filling, skipping, and removing Play sends requires a Play session.

Skill tools

Available tools link to the references they need. Load the matching reference before constructing a design, filter, or report. References for unavailable tool families are hidden too. Product documentation is available at Conversion Docs; clients can also connect its separate public MCP server at https://docs.conversion.ai/mcp.

Runtime limits

MCP has no Conversion sandbox. It does not expose shell commands, browser sessions, image generation, file uploads, or CSV import/export workflows that read or write sandbox paths. Your client’s local filesystem is separate from Conversion. Use existing hosted images from the Media library. To add an image, upload it in Conversion first. Slack, Linear, and Airtable tools tied to an agent’s integration session are also unavailable; gated Airtable setup lookups are available independently. See Differences from chat for context and approval behavior.