Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

MCP

Connect AI assistants to Cymbal with the Model Context Protocol (MCP) so they can draft campaigns, pages, automations, and more on your behalf.

Cymbal’s Model Context Protocol (MCP) connector lets AI assistants (Cursor, Claude, ChatGPT, and other MCP-compatible tools) work inside your Cymbal organization — draft and edit email/SMS campaigns, landing pages, automations, contacts, and more. You finish anything that goes live in Manager.

Status: Product beta

Connect

Connector URL: https://mcp.cymbal.co/connect

  1. In your AI assistant, add a new MCP server / connector.

  2. Paste the connector URL above.

  3. When prompted, sign in to Cymbal in the browser (Manager opens /mcp-connect). Approve access for the organization you want the assistant to use.

  4. After you connect, the assistant can call Cymbal tools using your session.

Tips:

  • Use a host account that already has access to the right organization in Manager.

  • If auth fails or tools return unauthorized, disconnect and reconnect the MCP server, then sign in again.

What assistants can do

Read organization data such as events, contacts, campaigns, automations, pages, ads, sources, billing, metrics, tags, and lists.

Draft and edit (without going live):

  • Create, edit, test, and duplicate email/SMS campaigns

  • Create and edit landing pages (not publish)

  • Create, edit, and test automations (not turn them on)

  • Manage contacts, tags, lists, events, settings, domains, and integrations

  • Reply in inbox, manage style presets, and upload images

What assistants cannot do

These still require Manager (or are blocked entirely):

  • Publish, send, or schedule campaigns — or cancel / stop / resume a live send

  • Publish, unpublish, or schedule landing pages

  • Launch, pause, or resume Meta ads, or enable automated carousels

  • Turn automations on, or seed the default live SMS welcome

  • Delete contacts, campaigns, pages, or other records

  • Partner API, public fan pages, webhooks, or admin-only actions

  • Change billing, payment methods, text balance top-ups / auto recharge, or owner-level team actions (remove members, change roles, invite owners) — those require an org Owner; non-owners get org owner access is required

Recommended workflow

  1. Ask the assistant to work in the correct organization.

  2. Have it draft the campaign, page, or automation.

  3. Review the draft in Manager via the links it returns.

  4. You publish, send, schedule, or enable — the assistant should not do those steps.

Related

  • Partners API — ticketing partner ingest and page discovery API

PreviousPartners API
NextWhy Cymbal?

Last updated