Connect Your CRM to Any AI (MCP)

• “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 right now?”

Eight read-only tools are exposed: search_contacts, get_contact, list_deals, list_tasks, get_revenue_summary, list_meetings, get_meeting_summary, and search_call_transcripts (semantic search across every recorded call; Pro plan).

Keys with the write scope also get import_call_transcript: paste or bridge a call transcript in (for example, fetched from another notetaker's MCP server, like Otter's) and Salescadia creates the meeting on the right contact and runs its full analysis — AI summary, coaching score, talk-time analytics, and a drafted follow-up. Try: “Pull yesterday's Acme call from Otter and import it into Salescadia.”

1. In Salescadia, open Settings → Integrations and find the Zapier & API Keys card.
2. Click Create API Key. The read scope is all the MCP server needs for querying; add the write scope too if you want import_call_transcript.
3. Copy the key (it starts with mm_live_) — it is shown once. Treat it like a password: it grants read access to your workspace's CRM data, and you can revoke it any time from the same card.

The server lives at https://www.salescadia.com/api/mcp (Streamable HTTP). Two ways to authenticate: sign in with your Salescadia account (OAuth — used by claude.ai) or an API key in the Authorization header (Claude Code, Cursor, custom agents).

Claude.ai & Claude Desktop — no API key needed

In claude.ai, 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 — no key to copy. (You can skip Step 1 entirely for this path.)

Claude Code

claude mcp add --transport http salescadia https://www.salescadia.com/api/mcp \
  --header "Authorization: Bearer mm_live_YOUR_KEY"

Cursor / Windsurf / VS Code (mcp.json)

{
  "mcpServers": {
    "salescadia": {
      "url": "https://www.salescadia.com/api/mcp",
      "headers": { "Authorization": "Bearer mm_live_YOUR_KEY" }
    }
  }
}

Custom agents (Claude API, OpenAI, LangChain, etc.)

Any MCP SDK can connect over Streamable HTTP with the same URL + header. The server is stateless — no session setup beyond the standard initialize handshake.

Quick smoke test from a terminal:

curl -s https://www.salescadia.com/api/mcp \
  -H "Authorization: Bearer mm_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

You should get back the tool list as JSON. Then ask your assistant something like “search my Salescadia contacts for Acme” and watch it call the tools.

• Read-only by default. With a read-scope key, every tool is a read — nothing the AI does can modify CRM data. The one write tool, import_call_transcript, only appears on keys you explicitly grant the write scope, and it only ever adds meeting records — it can't modify or delete anything existing.
• Workspace-scoped.A key can only see its own workspace's data — the same isolation our Zapier and Clay integrations use.
• Revocable. Deactivate a key in Settings and every connected AI loses access immediately.
• Anything the AI reads becomes part of that AI conversation — connect assistants you trust with your CRM data.

• 401 Unauthorized — the header must be exactly Authorization: Bearer mm_live_...; check the key wasn't revoked or expired.
• Transcript search says Pro required — semantic call-transcript search follows the same plan gate as the in-app Ask Anything feature.
• Stuck? Contact support.