Every CRM vendor shipped an AI assistant in the last two years. Almost all of them are the same thing: a chat panel bolted to the side of the app, able to answer questions about the page you are already looking at.
That is a demo, not a capability. The useful version is the opposite — your CRM available to whatever assistant you already use, doing real work, under the same rules as a person.
What we built instead
Pointof-CRM runs a Model Context Protocol server. It exposes 31 tools covering the records that matter: searching, creating and updating contacts, organizations, opportunities, tasks, quotes, orders and invoices.
It is a remote server, not a package to install. You point your client at the endpoint and authenticate with a token:
POST https://<your-workspace>/api/mcp
Authorization: Bearer <token>Generate the token under Settings → Integrations → AI Tool Access. From there, Claude Desktop, Cursor, a cron job or your own script all talk to the same surface — there is no SDK to install and no glue code to maintain.
The part that actually matters: permissions
An agent that can write to your CRM is a security question before it is a productivity one. The obvious failure is an integration that runs as an admin because that was easier.
Ours does not. Every MCP call resolves to a real user or API key, and every tool goes through the same role check the web app uses. An SDR's agent cannot delete a contact, because an SDR cannot delete a contact.
If the answer to “what can this agent do?” is different from “what can this person do?”, you have built two permission systems and you will eventually disagree with yourself.
Writes land in the same audit log as human actions, attributed to the caller. When you review who changed a deal last quarter, agents appear in that list beside everyone else — not in a separate integrations log nobody reads.
What this looks like in practice
- Ask your assistant which deals closing this month have gone quiet, and get an answer from live data rather than an export.
- Have a nightly job aggregate the pipeline and post the delta, without writing a reporting integration.
- Draft a quote from a spoken brief, in whichever of your currencies the customer bills in.
None of that needs a chat panel. It needs the CRM to be addressable — which, if you have modules and an API and a permission model, it very nearly already is.