Integrations

Connect Your AI to the CRM (MCP)

Ask Claude, Cursor, or any MCP-capable assistant questions about your own contacts, deals, revenue, and call transcripts.

1What it does

Salescadia hosts a Model Context Protocol (MCP) server — the open standard AI assistants use to reach outside tools. Connect it once and the AI you already use can answer questions from your live CRM:
  • “Which open deals haven't had a touchpoint in two weeks?”
  • “Summarize my last three meetings with Acme and draft next steps.”
  • “What objections did prospects raise about pricing this month?”
  • “What's our active MRR and how many deals are open?”
Eight read-only tools are exposed: contact search and detail, deals, tasks, revenue summary, meetings, AI meeting summaries, and semantic search across every recorded call transcript (Pro plan).

2How to connect

Claude.ai or Claude Desktop (easiest — no key needed): open Settings → Connectors → Add custom connector, paste https://www.salescadia.com/api/mcp, and click Connect. You'll be sent to Salescadia to sign in and approve read-only access. Claude Code, Cursor, and custom agents (API key):
  1. Open Settings and find the Zapier & API Keys card. Create a key with the read scope and copy the mm_live_... value — it is shown once.
  2. Add the server to your assistant with the key in the Authorization header. The server URL is https://www.salescadia.com/api/mcp.
For Claude Code it is one command:
claude mcp add --transport http salescadia https://www.salescadia.com/api/mcp --header "Authorization: Bearer mm_live_YOUR_KEY"
Cursor, Windsurf, and custom agents use the same URL and header — copy-paste configs live in the full setup guide.

3Security

  • Read-only. Nothing the AI does through this connection can change or delete CRM data.
  • Workspace-scoped. A key only sees its own workspace — the same isolation the Zapier and Clay integrations use.
  • Instantly revocable. Deactivate the key in Settings and every connected AI loses access immediately.
  • Anything the AI reads becomes part of that AI conversation, so connect assistants you trust with CRM data.

4Troubleshooting

  • 401 Unauthorized — the key must be sent as an Authorization: Bearer mm_live_... header (this endpoint refuses keys in the URL), and the key must be active and unexpired.
  • 403 Forbidden — the key lacks the read scope. Create a read-scoped key in Settings.
  • Transcript search says Pro required — call-transcript search follows the same plan gate as the in-app Ask Anything feature.