Model Context Protocol (MCP) is the emerging standard for AI agents to talk to real systems.
TL;DR
unLocked CRM is the first insurance CRM with a native MCP server. Built on mcp-lite + Hono, it exposes 16 CRM resources as native tools for Claude, Cursor, ChatGPT, and any MCP-compliant client — using the same API keys as the REST API.
Key Takeaways
- MCP is the emerging standard for AI agents to call external systems uniformly
- unLocked exposes 16 resources with full CRUD + bulk ops as MCP tools
- Same x-api-key / OAuth Bearer auth works across MCP and REST
- OpenAPI 3.1 auto-discovery for ChatGPT, Postman, SDK generators
- HMAC-signed webhooks with exponential-backoff retries and DLQ
For two years, "AI in your CRM" mostly meant a chat box bolted onto a sidebar. The next era looks very different: external AI agents — Claude Desktop, Cursor, ChatGPT Custom GPTs, in-house LangChain stacks — talking directly to your CRM through a standard protocol. That standard is the Model Context Protocol (MCP), and unLocked CRM is the first insurance CRM to ship a native MCP server.
What MCP Actually Is
MCP is an open spec for exposing tools, resources, and prompts to LLM clients in a uniform way. Instead of writing a custom Zapier-style adapter for every agent platform, you stand up one MCP server and every compliant client — Claude, Cursor, ChatGPT, Continue, Cline — can use it the same day.
What's Live in unLocked
- MCP server endpoint built on
mcp-lite+ Hono, deployed as a Supabase Edge Function - 16 CRM resources exposed as native tools: contacts, pipelines, policies, commissions, tasks, quotes, documents, carrier appointments, licensing, notes, tags, users, webhooks, files, reports, and automations
- Bulk operations on every collection (not just single-record CRUD)
- Same auth as REST — your existing
x-api-keyor OAuth Bearer token works for MCP without re-issuing credentials
Why This Matters for Independent Agents and Agencies
Picture a Friday afternoon: you ask Claude "build me a list of every Medicare client turning 70 next quarter who hasn't had an annual review, and draft a personalized outreach SMS for each." With MCP, Claude reads your contacts and policies through CRM tools, drafts the messages, and queues them — all without leaving the chat. No exporting CSVs, no manual imports.
Auto-Discovery via OpenAPI 3.1
Alongside MCP, we publish a live OpenAPI 3.1 document. Any tool that speaks OpenAPI — ChatGPT Custom GPTs, Postman, Insomnia, Stainless SDK generators — auto-discovers every endpoint and schema. No human-maintained docs drifting out of sync with the implementation.
Hardened for Production Partners
Webhooks are HMAC-SHA256 signed in the Stripe t=…,v1=… format. Failed deliveries retry on a 1-minute → 6-hour exponential ladder and dead-letter after 6 attempts via a pg_cron-scheduled retry worker. Every response carries X-Request-Id and X-Api-Version headers for tracing.
The Strategic Read
Insurance CRMs that don't ship MCP and a real OpenAPI spec in the next 12 months will become invisible to the agent layer that buyers are starting to standardize on. Agents will increasingly ask "can my AI talk to it?" before "what does the UI look like?" — and the answer needs to be yes, natively.
Frequently Asked Questions
Do I need a separate API key for MCP?
No. The same x-api-key or OAuth Bearer token used for REST works for MCP.
Which clients are supported?
Claude Desktop, Cursor, ChatGPT Custom GPTs, Continue, Cline, plus anything that speaks REST + OpenAPI 3.1 (Zapier, Make, n8n, Postman).
Are webhook payloads signed?
Yes — HMAC-SHA256 in the Stripe t=…,v1=… format with replay protection.
Where This Fits In unLocked
- best CRM for insurance agents: How insurance CRMs compare on quoting, commissions, AI and price.