Install MCP
Wire CRM Doc into any AI in 60 seconds.
One install. Restart your client. Your AI now has 8 tools to build, edit, and deploy funnels into your CRM. Self-host the OSS server or use the hosted API. Either way, BYO AI keys.
How it fits together
You
Tell your AI what to build
Your AI
Claude, Cursor, ChatGPT…
MCP / REST
8 tools, BYO API key
CRM Doc API
Generates the funnel JSON
Your CRM
GoHighLevel live, more soon
Pick your client
3 live · 4 beta · 1 soonInstall for Claude Desktop
The reference MCP client. macOS + Windows + Linux. One command writes the config.
You need an API key first. Sign up (free) and mint one, or use a test key for evaluation.
Get an API key ›Writes to ~/Library/Application Support/Claude/claude_desktop_config.json. Restart Claude Desktop afterwards.
Verify it works
Restart your AI client, then ask:
Or hit the REST API directly:
Tools your AI now has
8 tools, hit the REST API at api.crmdoc.ai/v1/*.
| Tool | What it does |
|---|---|
list_templates | Browse 32 funnel templates by industry. Includes sourced benchmarks. |
create_funnel | Generate a funnel from a template, with field overrides. |
edit_funnel | Modify an existing funnel (rename stages, change waits, add steps). |
deploy_to_crm | Push pipeline, tags, fields, sequences, automations to your CRM. |
generate_landing_page | Render a landing page from the funnel + your brand tokens. |
add_automation | Wire a trigger + actions into the funnel. |
list_builds | Read recent deploy attempts. Filter by funnel, status, target. |
get_build | Fetch one build with its step-by-step log + diff. |
Troubleshooting
Restarted my AI client but I can't see the tools.+
Confirm the config file was written. For Claude Desktop, open the developer log: View › Developer › Open MCP Logs. Look for a "crmdoc" entry. If it failed to spawn, the most common cause is the API key env var not being set in the launching shell. For Cursor, check ~/.cursor/mcp.json exists.
I see the tools but a call returns 401 Unauthorized.+
Your key was revoked or expired. Mint a fresh one at Account › API keys; the old one stops working immediately on revoke.
A deploy call returns "no CRM credential connected".+
You need to connect a CRM in Account › Integrations before deploys run for real. Until then, builds run in dry-run mode and return the plan without applying it.
The MCP install command says "permission denied".+
npx needs write access to your home directory and the AI client's config path. On macOS, check System Settings › Privacy › Full Disk Access if you have aggressive security tools running.
I want to run this in CI without my personal AI client.+
Skip the MCP and call the REST API directly. Same Bearer auth, same tools, no MCP runtime needed.
Can I self-host the MCP server?+
Yes. The MCP server is MIT-licensed at github.com/anteai/crmdoc-mcp. Clone, npm install, npm run dev. Set CRMDOC_API_KEY to point at the hosted API, or run a self-hosted CRM Doc API too (more work; docs landing in v0.3).
Get your key + ship your first funnel.
Self-host the engine free, or start a 14-day hosted trial, no card. Real CRM deploys on GoHighLevel today, HubSpot in v0.3.