Connect your AI to your automations
Every automation in your cmdk workspace doubles as a typed tool. Point Claude, ChatGPT, Cursor, Slack, WhatsApp, or a plain script at it and the run executes on cmdk, with your connected accounts, approvals, and run history.
AI agents (MCP)
Your workspace exposes an MCP server. Add it once and every automation appears as a tool the AI can call, typed inputs included. Two extra tools come along: check_run and list_automations.
Claude (claude.ai & Desktop)
01Settings → Connectors → Add custom connector. Claude's dialog has no header field, so append your API key to the URL path:
https://cmdk.io/api/mcp/<your key>
Claude Code
02One command in your terminal:
claude mcp add cmdk --transport http https://cmdk.io/api/mcp \ --header "Authorization: Bearer <your key>"
Cursor / any MCP client
03Add to .cursor/mcp.json (or your client's MCP config):
{
"mcpServers": {
"cmdk": {
"type": "http",
"url": "https://cmdk.io/api/mcp",
"headers": {
"Authorization": "Bearer <your cmdk API key>"
}
}
}
}ChatGPT
04Settings → Connectors → Advanced → Developer mode → add an MCP server with the same URL and Authorization: Bearer <your key>.
https://cmdk.io/api/mcp
Slack
- In cmdk, open Channels & API access and click Connect Slack (a workspace admin approves the install).
- Mention the bot in any channel or DM it: “@cmdk run the morning digest”.
- When an automation needs a person, it posts a card with buttons to the channel you pick per automation, and the answer resumes the run.
- Link your phone number on the Channels & API access page.
- Message the workspace number to run automations.
- Escalation questions arrive as button messages; replying in plain text answers them.
Plain HTTP
Anything that can send an HTTP request can start a run. Pass "wait": true to get the result in the same call, or poll with the returned run id.
curl -X POST https://cmdk.io/api/automations/<automation-id>/invoke \
-H "Authorization: Bearer <your key>" \
-H "Content-Type: application/json" \
-d '{"inputs": {"port": "Delfzijl"}, "wait": true}'Safe by construction
External callers never touch your connected accounts directly. Runs execute on cmdk with the workspace's own permissions, the approval rules you set per app, and a full run history. Revoke an API key and every door it opened closes.