For developers
104 tools. 409 endpoints. Built so AI agents can drive your CRM the same way your team does — with permissions, audit logs, and dry-run safety.
{
"mcpServers": {
"conduyt": {
"command": "npx",
"args": ["tsx", "src/index.ts"],
"cwd": "~/path/to/conduyt-mcp",
"env": {
"CONDUYT_API_URL": "https://conduyt.app",
"CONDUYT_API_KEY": "cdy_your_key_here"
}
}
}
}
Drop that into Claude Desktop. Restart. Done.
30-second primer
Model Context Protocol is an open standard from Anthropic that lets AI models connect to external tools. Think of it like USB for AI: any MCP-compatible client can plug into any MCP server. Claude Desktop, Claude Code, Cursor, custom agents — they all speak it.
Conduyt ships with a native MCP server. 104 tools across 20 modules. Drop in your API key and your AI client has full CRM access through a typed, validated, audited interface.
If you’d rather not use MCP, the REST API works the same way. Same auth, same permissions, same audit log. More on that below.
Tool catalog
20 modules, 104 tools, one consistent naming convention (conduyt_<module>_<action>). Grouped by domain for navigation.
Get started in minutes
Claude calls conduyt_deals_list and answers in plain English.
AI-driven CRM ops without leaving your shell.
Whatever speaks MCP, works.
Not using MCP?
Not every team is on MCP yet. Some are still on Zapier, n8n, or rolling custom agents against raw HTTP. We support those, too.
The REST API mirrors the MCP server one-to-one. Same auth (Bearer token, cdy_ prefix). Same permissions (scoped keys, per-domain access). Same audit log. Same 409 endpoints across 30 domains.
# Pull the dashboard summary curl https://conduyt.app/api/v1/dashboard/summary \ -H "Authorization: Bearer cdy_your_key_here" \ -H "Content-Type: application/json"
Or call our schema-discovery endpoint, which returns the full catalog in one response:
curl https://conduyt.app/api/v1/schema/api-catalog \ -H "Authorization: Bearer cdy_your_key_here"
That last one is what your AI agent should call first. It’s a self-describing index of every endpoint, parameter, and return type. Your agent reads it, learns the CRM, then drives.
Guardrails, not gates
Open API access without controls is what makes a CTO refuse the meeting. So we built six primitives specifically for AI agents:
Read-only, write, or admin tiers. Restrict to specific modules (e.g., contacts only, no user management). Per-IP allowlisting available.
Add ?dry_run=true to any mutation. Returns what would happen without actually doing it. Perfect for letting your AI propose changes before you approve.
Run a full transaction inside a Postgres rollback. Use for “what if” simulations or AI experimentation. Nothing persists.
Destructive actions (delete, bulk reassign) require a 5-minute-TTL handshake. Your AI proposes, you confirm with a separate API call.
Default is 120 requests per minute per API key, enforced via Upstash at the Edge middleware layer. Hits the limit, gets a 429 with X-RateLimit-Reset.
Every API call logged with who (key ID), what (endpoint + payload), when, where (IP). 90-day retention. Exportable as JSON or CSV for your SIEM.