MCP CRM
The CRM that speaks MCP.
Model Context Protocol isn't a chatbot plugin. It's how Fresno exposes the same CRM tools your team uses — contacts, deals, tasks, automations — to any agent that speaks MCP.
MCP, concretely.
MCP (Model Context Protocol) is a standard way for an agent to call tools over HTTP. Fresno's endpoint is JSON-RPC 2.0 athttps://app.example.com/mcp — the same capability layer the rest of the product uses, not a parallel AI stack.
One HTTP endpoint
Clients discover and call tools on POST /mcp. Claude, Cursor, and any other MCP client hit the same URL with the same schemas.
CRM verbs, not a chat wrapper
Search and update contacts and companies, list and move deals, create and complete tasks, log activities, CRUD notes, search synced email, list meetings, fetch call recordings and transcripts, list or enroll sequences, run pipeline-by-stage and win-rate reports, list or create automations, and run structured record queries.
Same tools as the product
Tenant isolation, dedup, and history come from the existing entity modules. An agent doesn't get a shadow API with different rules.
Connect in one command.
The same add command works for Claude; other MCP clients point at the same endpoint. Authorize once — no long-lived key in a config file if you use OAuth.
claude mcp add --transport http fresno https://app.example.com/mcp
Prefer a different client? Use the endpoint above with any MCP HTTP transport. Developers who want webhooks, custom objects, and SSO should start at Fresno for developers.
Ask it like you'd ask a teammate.
These are the kinds of prompts an MCP client can run against live CRM data — reads and writes, only with the scopes you grant.
- How many deals closed this quarter, by rep?
- List deals stuck in the same stage over 60 days.
- Create a task to call Acme before Friday.
- What's in the pipeline for Acme?
- Add the attendees from this thread as contacts.
- Log a call on the Acme deal and complete the follow-up task.
OAuth-scoped. Revocable.
Access is OAuth 2.1 (with personal tokens as a fallback). Writes are a separate scope. You can revoke a client without rotating the rest of your stack.
Read your records
Search and fetch contacts, companies, deals, pipelines, tasks, activities, notes, synced email, meetings, call transcripts, sequences, automations, and aggregated pipeline/win-rate reports. Enough for briefing, reporting, and “what's stuck?” without mutation rights.
Writes are opt-in
Create and update records, complete tasks, log activity, write notes, enroll sequences, and create automations only if you grantcrm:write. A read-only agent cannot silently mutate the pipeline. Write tools advertise MCP confirmation annotations.
Kill the grant, not the CRM
Disconnect Claude or any other client from your profile. The token dies; your data and the rest of your integrations stay put.
Keep going
This page is the MCP story. The rest of Fresno is still a full CRM — sequences, scoring, automation — with that same capability layer underneath.