What is it?
MCP is a standard way for AI assistants to talk to other tools. Once you connect ChatAutoDM, you can ask your assistant things like:
- “How many DMs did we send this week, and which automation did best?”
- “List my active automations and tell me which ones have never run.”
- “Which FAQs does my AI assistant use? Find gaps.”
- “Draft a comment-to-DM automation that sends the price list when someone comments PRICE.”
Each connection uses an API key tied to one workspace. The assistant can only see that workspace.
Before you start
- 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.
- Use an AI client that supports remote MCP servers over HTTP. Apps that let you sign in (ChatGPT, Claude) connect with one click; command-line and editor tools use an API key.
Easiest way: sign in (ChatGPT, Claude and other apps that ask for OAuth)
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 / custom MCP server screen in your app.
- Paste the server address:
https://mcp.chatautodm.com/mcp. - Choose OAuth for authentication.
- When the sign-in window opens, sign in to ChatAutoDM, pick the workspace and the permissions, and press Allow.
You can disconnect the app at any time in Settings → MCP (it appears there as a connected app). Permissions work the same as for keys, and Publish automations is never selected for you.
Step 1: Create an API key
For command-line and editor tools that do not offer a sign-in screen:
- Open Settings → MCP in your workspace.
- Click Create API key and give it a name, such as “Claude on my laptop”.
- Tick only the access the assistant needs (see the table below). Turn on Create automation drafts only if you want it to draft automations.
- Choose when the key expires (30, 90 or 365 days).
- Copy the key straight away. It is shown once and cannot be retrieved later. If you lose it, create a new one.
You can have up to five active keys per workspace and can revoke any key at any time from the same page.
Step 2: Add it to your AI client
The server address is https://mcp.chatautodm.com/mcp. Replace <your API key> with the key you copied. Client settings change over time, so if a snippet does not work, check your client’s own MCP documentation for how to add a remote HTTP server with a header.
Claude Code
claude mcp add --transport http chatautodm https://mcp.chatautodm.com/mcp --header "Authorization: Bearer <your API key>"Cursor
Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then restart Cursor.
{
"mcpServers": {
"chatautodm": {
"url": "https://mcp.chatautodm.com/mcp",
"headers": { "Authorization": "Bearer <your API key>" }
}
}
}Codex
Add to ~/.codex/config.toml, then set the key in the terminal you start Codex from and restart Codex. A Codex app that is already open will not see the key.
[mcp_servers.chatautodm]
url = "https://mcp.chatautodm.com/mcp"
bearer_token_env_var = "CHATAUTODM_API_KEY"export CHATAUTODM_API_KEY="<your API key>"VS Code
Add to .vscode/mcp.json in your project.
{
"servers": {
"chatautodm": {
"type": "http",
"url": "https://mcp.chatautodm.com/mcp",
"headers": { "Authorization": "Bearer <your API key>" }
}
}
}Claude Desktop
Claude Desktop needs a small bridge for servers that use an API key (requires Node.js). Open Settings → Developer → Edit Config, add this and restart the app.
{
"mcpServers": {
"chatautodm": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.chatautodm.com/mcp", "--header", "Authorization:${CHATAUTODM_AUTH}"],
"env": { "CHATAUTODM_AUTH": "Bearer <your API key>" }
}
}
}Other clients
Most clients that support remote MCP accept this format.
{
"mcpServers": {
"chatautodm": {
"url": "https://mcp.chatautodm.com/mcp",
"headers": { "Authorization": "Bearer <your API key>" }
}
}
}Step 3: Try it
Ask your assistant:
Use ChatAutoDM to show my workspace overview and list my automations.If it answers with your plan and automations, you are connected.
What the assistant can do
Read tools
| Tool | What it returns | Key access needed |
|---|---|---|
| get_workspace_overview | Plan, subscription status and connected Instagram / WhatsApp channels. | Workspace overview |
| get_usage_limits | Plan limits, current usage and remaining allowance (approximate). | Workspace overview |
| list_automations | Your automations, newest first. Filter by type, active state or status. | Automations |
| get_automation | Configuration summary and flow outline of one automation. | Automations |
| list_faqs | FAQ entries used by the AI assistant (long text is truncated). | Knowledge base |
| list_knowledge_sources | Knowledge source titles, types and status. Document content is not included. | Knowledge base |
| list_contacts | Contacts with masked email and phone. Search matches username and name. | Contacts |
| get_analytics_summary | Daily DMs sent, link clicks and seen counts for 7, 30 or 90 days, plus AI reply totals. | Analytics |
Draft tools (optional)
Available only to keys created with Create automation drafts.
| create_story_reply_draft | Draft an automation that replies to story replies. |
| create_comment_to_dm_draft | Draft an automation that DMs people who comment on a post. |
| create_dm_autoresponder_draft | Draft an automation that answers incoming DMs by keyword. |
Drafts are saved inactive. To use one, open it in ChatAutoDM, review the messages and links, and switch it on yourself. A workspace can hold up to 25 pending drafts created this way.
Publish tools (optional, off by default)
Available only to keys created with Publish automations. They work only on automations created through MCP; anything you built in the app is untouched.
| publish_automation | Turn a draft the assistant created ON. It then messages real people when its trigger matches. Needs confirmGoLive: true. |
| deactivate_automation | Turn an assistant-created automation OFF again. |
Publishing follows the same rules as turning an automation on in the app: your plan's active-automation limit applies, and button links are tracked. On top of that, a workspace can publish at most 10 times in 24 hours, and you get an email every time an assistant publishes. You can turn anything off from the app or with deactivate_automation.
Safety and privacy
- One workspace per key. A key cannot see other workspaces, and the assistant cannot choose a different one.
- It cannot send messages by itself. There is no tool for sending DMs. Drafts stay inactive until you switch them on, unless you gave that key the optional Publish permission.
- Publishing is a separate, opt-in permission. Only turn it on for an assistant you trust, review what it drafts, and check your email: you are notified on every publish.
- Contact details are masked. Emails and phone numbers are partially hidden, and access tokens are never exposed.
- You control the access. Each key only has the areas you ticked, expires on the date you chose, and can be revoked instantly.
- Treat keys like passwords. Anything you paste a key into can read the data it allows. Do not put keys in shared files, screenshots or chats. If one is exposed, revoke it in Settings → MCP.
- Usage is limited and logged. Requests are rate-limited, and each call is recorded without message content.
Troubleshooting
- 401 / “Invalid API key”: the key is wrong, expired or revoked. Create a new one.
- 403 / “MCP is not enabled for this workspace”: MCP has not been turned on for this workspace yet.
- 429: too many requests. Wait a minute and try again.
- Tool missing: the key was created without that access. Create a new key with the access you need.
- Client cannot connect at all: check that it supports remote HTTP MCP servers with a custom header, and that the URL is exactly
https://mcp.chatautodm.com/mcp.