MCP overview
What the Model Context Protocol is, why Harmonia ships it, and how scopes work.
Harmonia ships a built-in Model Context Protocol server. MCP is the open standard Anthropic published in late 2024 for letting AI clients — Claude Desktop, Cursor, Windsurf, Zed — talk to external tools through a single uniform interface.
Most CRMs that "do AI" hand you a sidebar chatbot. Harmonia's MCP server is different: it exposes the real CRM surface to whichever AI client you already use. The AI can list opportunities, draft an email, move a deal, log a call, summarize a pipeline, or place a call — bounded by OAuth scopes you grant.
What you get
- 37 tools spanning contacts, opportunities, accounts, conversations, calendars, comms, workflows, and reporting
- 3 prompt templates — daily pipeline brief, stale-deal alert, lender-match brief — that Claude can run on demand
- Per-tenant scoping — the AI only sees the org you connected
- Per-action audit log — every tool call is recorded with timestamp, user, and arguments
Scopes
The MCP server uses a four-scope OAuth model:
| Scope | Grants |
|---|---|
mcp:read | Read access to non-sensitive entities (contacts, opps, accounts) |
mcp:write | Create / update / delete on those same entities |
mcp:comms | Send email, SMS, place calls — always gated by the outbound kill switch |
mcp:admin | User management, org settings, audit log read |
You decide which scopes each connected client gets. A "research" client
can be mcp:read only. A "do my outreach" client can be
mcp:read,write,comms. Revoke at any time from Settings → MCP.
What plans include it
| Plan | MCP access |
|---|---|
| Starter | — |
| Pro | mcp:read (Claude Desktop reads) |
| Business | Full — read, write, comms, admin |
| Custom | Full + bring-your-own tools |
Next
- Connect Claude Desktop — step-by-step
- Tools reference — every tool, every arg