Connecting Claude and other AI assistants to Marketing

Last updated:

What this gives you

Chorum can connect to AI assistants such as Claude (Cowork, claude.ai and Claude Desktop), Cursor and other tools that support MCP (Model Context Protocol). Once connected, you can ask the assistant about your marketing in plain English, and with write access it can create drafts for you:

  • "Which of last month's email broadcasts had the best click rate?"
  • "Which mailing list grew fastest this quarter, and which forms did the sign-ups come from?"
  • "Draft a LinkedIn post and a shorter X post announcing our new service, and save them as drafts."
  • "Plan a four-week spring campaign with an awareness objective and create it in Chorum."

The assistant works with your live Chorum data, only sees what your access allows, and every action is logged against your key.

Choose your connection

  • Personal connection (recommended): one connector for you, covering every module you have been given access to, including Marketing. See Your personal AI connection.
  • Per-customer key: for agencies and MSPs. A key limited to one customer's marketing, which you can use yourself or give to that customer's team. See Per-customer AI keys for agencies.

Either way you end up with a connector URL that contains your key, ending in ?key=pk_....

Add the connector to your AI assistant

Claude (Cowork, claude.ai or Claude Desktop)

  1. Open Settings, Connectors and choose Add custom connector.
  2. Give it a name, such as "Chorum".
  3. Paste your full connector URL, including ?key=pk_....
  4. Leave the OAuth Client ID and Secret blank; the key in the URL handles sign-in.
  5. Choose Add, then start a new conversation and ask "What's on my marketing dashboard?"

Cursor

Add an MCP server that uses your connector URL, for example in Cursor's MCP settings file:

{
  "mcpServers": {
    "chorum": { "url": "https://YOUR-WORKSPACE.chorum.io/api/mcp/rpc?key=pk_YOUR_KEY" }
  }
}

Other tools and scripts

Any client that supports MCP over HTTP can use the same URL. Scripts can send the key in an Authorization: Bearer pk_... header instead of putting it in the URL.

What the assistant can do

  • Read access lets it read your campaigns, email broadcasts, mailing lists and subscribers, social posts and accounts, landing pages, list growth and sign-up sources, and campaign results.
  • Write access also lets it create drafts, such as email broadcasts, templates, social posts, campaigns, mailing lists and landing pages, and make the changes you ask for. Nothing is sent to your contacts unless you explicitly ask it to send.

Always review what the assistant drafts before you publish or send it.

Keeping it safe

  • Your connector URL contains your key, so treat it like a password. Do not paste it into shared chats or documents.
  • Keys are shown once, when you create them. Chorum only stores a scrambled copy.
  • If a key may have leaked, revoke or regenerate it straight away. Anything using the old key stops working immediately.
  • Per-customer keys cannot reach any other customer's data, even if someone tries.

Troubleshooting

  • "Couldn't register" or a request for an OAuth Client ID: the URL reached Chorum without a valid key. Check you pasted the whole URL, including the key itself, not just ?key=. Then delete the connector and add it again; Claude remembers the failed attempt until you do.
  • The connector worked, then stopped: the key was regenerated or revoked. Update the connector with the new URL.
  • Fewer tools than expected: your key only covers the modules and access level you were granted. Ask an admin to grant Marketing access (write access for drafting), then refresh or reconnect the connector.
  • Tools return no data: a per-customer key only sees that customer's workspace. Check which customer the key is for.

Related articles