Connect AI assistants with MCP

Let Claude, Cursor, Codex and other AI tools read your workspace and draft automations safely.

6 min read

MCP (Model Context Protocol) lets AI assistants such as Claude, Cursor and Codex connect to your ChatAutoDM workspace. Once connected, you can ask them about your automations, analytics and FAQs, or ask them to draft a new automation.

What it can and cannot do

  • Can read: your workspace overview and plan, usage and limits, automations, FAQs and knowledge sources, contacts (with email and phone partly hidden) and analytics.
  • Can draft (optional): story reply, comment-to-DM and DM auto-responder automations, saved as inactive drafts.
  • Can publish (optional, off by default): with the separate Publish automations permission it can turn its own drafts on and off. A published automation messages real people.
  • Cannot send messages by itself. There is no tool for sending a DM. Unless a key has the Publish permission, nothing it creates runs until you switch it on yourself.
  • Sees one workspace only. Each key belongs to a single workspace.

Who can use it

You must be an owner or admin of the workspace. MCP is rolling out gradually: if you do not see an MCP tab in Settings, it is not enabled for your workspace yet.

Easiest way β€” sign in (ChatGPT, Claude and other apps)

If your app has a place to add a custom connector or custom MCP server, you do not need an API key.

  • Open the custom connector screen in your app.
  • Paste the server address (shown in Settings β†’ MCP).
  • Choose OAuth for authentication.
  • When the sign-in window opens, sign in to ChatAutoDM, pick your workspace and the permissions, and press Allow.

You can disconnect the app any time in Settings β†’ MCP. Publish automations is never selected for you. For command-line and editor tools, use an API key as described below.

Step 1 β€” Create an API key (for command-line and editor tools)

  • Open Settings β†’ MCP.
  • Click Create API key, give it a name such as "Claude on my laptop", and tick only the access you need. Turn on Create automation drafts only if you want drafts.
  • Leave Publish automations off unless you want the assistant to be able to turn drafts on. See "Publishing" below.
  • Choose an expiry (30, 90 or 365 days).
  • Copy the key right away. It is shown once. If you lose it, create a new one.

Step 2 β€” Connect your tool

Every tool needs two things: the server address and your key. The server address is:

Server address
https://mcp.chatautodm.com/mcp

In the snippets below, replace the highlighted <your API key> with the key you copied. The Connect an AI client card in Settings β†’ MCP shows the same snippets with copy buttons.

Claude Code

Run this once in your terminal:

Terminal
claude mcp add --transport http chatautodm https://mcp.chatautodm.com/mcp --header "Authorization: Bearer <your API key>"

Cursor

Open (or create) the file ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project. Add this, save, then restart Cursor:

mcp.json
{
  "mcpServers": {
    "chatautodm": {
      "url": "https://mcp.chatautodm.com/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

Codex

Add this to ~/.codex/config.toml:

~/.codex/config.toml
[mcp_servers.chatautodm]
url = "https://mcp.chatautodm.com/mcp"
bearer_token_env_var = "CHATAUTODM_API_KEY"

Then set your key in the terminal, and start (or restart) Codex from that same terminal. A Codex app that is already open will not see the key. On a Mac with the desktop app, run the export line, then open the app from that terminal (for example with the open -a command).

Terminal
export CHATAUTODM_API_KEY="<your API key>"

VS Code

Create a file named .vscode/mcp.json in your project and add:

.vscode/mcp.json
{
  "servers": {
    "chatautodm": {
      "type": "http",
      "url": "https://mcp.chatautodm.com/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

Claude Desktop

Claude Desktop needs a small helper for servers that use an API key. You need Node.js installed. Open Settings β†’ Developer β†’ Edit Config, add this, save, and restart the app:

claude_desktop_config.json
{
  "mcpServers": {
    "chatautodm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.chatautodm.com/mcp", "--header", "Authorization:${CHATAUTODM_AUTH}"],
      "env": { "CHATAUTODM_AUTH": "Bearer <your API key>" }
    }
  }
}

Any other tool

Most tools that support remote MCP servers accept the same format as Cursor above. You need a tool that can connect to a remote server over HTTP and send an Authorization header. Tools that only support signing in (OAuth) can use the sign-in option above.

Tip: Tool settings change over time. If a snippet does not work, look in your tool's own MCP documentation for how to add a remote HTTP server with a custom header, and use the server address and key above.

Step 3 β€” Try it

Ask your assistant:

Prompt
Use ChatAutoDM to show my workspace overview and list my automations.

If it answers with your plan and automations, you are connected.

Using drafts

When an assistant creates a draft, open it in ChatAutoDM, check the messages and links, and switch it on yourself. A workspace can hold up to 25 pending drafts created this way.

Publishing (optional)

If you gave a key the Publish automations permission, the assistant can turn its own drafts on, and off again. Only automations created through MCP are affected; anything you built in the app is never touched.

  • Publishing follows the same rules as switching an automation on in the app, including your plan's limit on active automations.
  • A workspace can publish at most 10 times in 24 hours.
  • You get an email every time an assistant publishes something.
  • To stop an automation, turn it off in the app, or ask the assistant to turn it off.

Tip: ask the assistant to show you the draft first, and only publish after you have read the messages and checked the links.

Keep your keys safe

  • Treat an API key like a password. Do not put it in shared files, screenshots or chats.
  • You can have up to five active keys per workspace.
  • If a key is exposed, open Settings β†’ MCP and click Revoke next to it. It stops working immediately.

Troubleshooting

  • Invalid API key (401): the key is wrong, expired or revoked. Create a new one.
  • MCP is not enabled for this workspace (403): MCP has not been turned on for your workspace yet.
  • Too many requests (429): wait a minute and try again.
  • A tool is missing: the key was created without that access. Create a new key with the access you need.
  • Your tool cannot connect: check that the server address is exactly the one above, and that the tool supports remote HTTP MCP servers with a custom header.

Was this article helpful?

Still can't find what you're looking for?

Our team is here to help.