A CRM built on MCP
Your CRM, any agent.
A complete CRM with an open agent interface. Use the assistant we host for you, or connect your own — Claude, Cursor, anything that speaks MCP. Same data, same tools, either way.
Two front doors. One capability layer.
The assistant we run and the agent you bring call the exact same scoped tools over your records. Neither is bolted on; neither is a second-class citizen.
The built-in assistant
An agent that already knows your CRM — no setup, no keys. Ask it to pull a report, draft follow-ups, or move a deal. The fastest way for anyone on the team to work with AI.
Try the assistant →Your agent, your endpoint
Point Claude, Cursor, or any MCP client at your Fresno endpoint. It reads and acts on your CRM with exactly the access you grant — authorized over OAuth, no pasted keys.
claude mcp add --transport http fresno https://app.example.com/mcpConnect your agent →
Ask it like you'd ask a teammate.
Plain language in, real work out — reads and writes, through either door.
- How many deals closed this quarter, by rep?
- Draft a follow-up to everyone I haven't emailed in 30 days.
- Create a task to call Acme before Friday.
- Which sequences have the best reply rate?
- Add the attendees from this thread as contacts.
- What's stuck in the pipeline over 60 days?
One capability layer
Every AI path calls the same tools you'd use by hand. There's no separate AI stack to trust, secure, or keep in sync.
Standard MCP, no lock-in
OAuth 2.1 and MCP discovery mean any compliant client connects today — and whatever the ecosystem ships next.
Yours to revoke
Scoped, revocable access. Writes are opt-in and gated, so an agent can never touch more than you allow.