The MCP server exposes the same catalog of actions Conversion AI uses in chat, with a few differences:
For how each tool behaves once your client calls it, and how editing differs from chat, see Differences from chat.
Reading and lookups
Read tools never change anything. They power the “answer questions about my data” side of Conversion AI.
| Area | Actions |
|---|
| Contacts | List, get, count, read events and automation runs, list opportunities, list fields, read distinct field values. |
| Companies | List a company’s opportunities. |
| Opportunities | List, get, count, list a deal’s contacts. (Opportunities are read-only; they sync in from your CRM.) |
| Audiences | List. |
| Emails | List blasts, workflow emails, and templates; get an email; read metrics and recipients. |
| Forms | List, get, read submissions. |
| Workflows | List, get, read runs and metrics. |
| Campaigns | List campaigns, items, members, tokens, types, and type statuses. |
| Folders | List top-level folders and folder contents. |
| Workspace | Read email settings and the business logo. |
| Sync | List sync batches and logs. |
Creating new assets
Over MCP, create tools write directly to your workspace; there’s no artifact preview step the way there is in chat. A new asset is created live but dormant: emails, forms, and workflows land as unpublished drafts. Nothing is sent, published, or activated; you still take that step yourself in Conversion.
| Area | Actions |
|---|
| Contacts | Create a contact, create a custom field, upload and process a CSV import. |
| Audiences | Create a static or dynamic audience. |
| Emails | Create a blast, workflow email, or template. |
| Forms | Create a form. |
| Workflows | Create a workflow. |
| Campaigns | Create a campaign, campaign type, type status, or token. Duplicate a campaign. |
| Folders | Create a folder, move assets between folders. |
Workflows are create-only. There’s no edit flow for an existing workflow. To change one, create a new workflow and switch to it. This matches Conversion AI in chat. Editing existing assets
To change an asset that already exists, the MCP server exposes raw, immediate-apply edit tools. Each one applies the change to your workspace the moment your client calls it; there’s no preview and no review step in Conversion. This is the biggest behavioral difference from chat; see Editing existing assets for the full comparison.
| Tool | What it changes |
|---|
update_email | Update an existing blast or workflow email: name, subject, preview, body, sender, topic, and (for blasts) recipients and scheduled send time. Partial: set only the fields you change. Blasts stay in draft. |
update_form | Update a form’s metadata: name, CRM-sync, and subscribe behavior. |
update_form_draft | Replace a form’s design (its draft FormData) with a complete definition. |
update_audience | Update an audience’s name, type, or dynamic filter. |
add_audience_contacts | Add specific contacts to a static audience. |
update_campaign | Update a campaign’s name or description. |
campaign_add_members | Add everyone matching a filter as campaign members. |
campaign_set_token_value | Set a campaign’s value for one token. |
campaign_update_member_status | Set a campaign member’s status. |
These tools apply immediately and accept partial updates, so set only the fields you intend to change. Edits to body or design fields (update_email’s data, update_form_draft’s draft) take the complete definition, not a diff, so read the current asset first. The onus is on your client to confirm before calling and to send only what it means to change.
| Tool | Loads the reference for |
|---|
learn_statement_semantics | The filter / statement query language used by audiences, campaign membership, and contact queries. |
learn_email_building | The EmailData JSON shape (components, theme, layout, merge fields). |
learn_form_building | The FormData JSON shape (components, hidden fields, theme, settings). |
learn_workflow_building | The workflow graph (nodes, edges, triggers, control flow). |
Call the matching skill tool before any tool that takes a body, design, statement, or filter argument. For example, load learn_email_building before create_email or update_email.
Not available over MCP
| Not available | Notes |
|---|
| Sandbox and file tools | Running code, reading and writing files, and uploading images run only in the chat sandbox, which doesn’t exist over MCP. Your client’s own environment is separate from Conversion. |
| Sending, publishing, activating | Building or editing an asset never sends a blast, publishes a form, or activates a workflow. Those stay manual steps in Conversion. |
| Deleting | The MCP server cannot delete contacts, audiences, emails, forms, workflows, campaigns, folders, fields, or tokens. |
| Editing live workflows | Workflows are create-only (see above). |
