
CRM Connector MCP server
Which MCP servers are CRM Connector's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry namecom.crm-connector/crm-connectorverified in the MCP registry
The registry name sits under crm-connector.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools26
- Server calls itselfcrm-connector
- Server version1.1.1
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 260 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- Keep approval on for send_request: they delete, send or pay without saying so.
- send_request change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer215 ms
- Space in an agent's context≈ 14,038 tokensthe definitions of all its tools (30), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results30 of 30 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · sync customers and invoices between GoHighLevel and accounting tools
- not sure · push field service appointments and jobs into GoHighLevel
- not sure · link contacts from HubSpot or Salesforce into GoHighLevel
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that delete, send or pay, marked as not destructive: send_request
- Tools that change data, on a server that answers without a sign-in: send_request
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
plan_integrationIntegrations (between two systems): Use when someone wants to set up a sync between two systems, for example "when a deal is won in our CRM, make a draft invoice in our accounting system" or "keep our customers and invoices the same in…
find_sync_optionsIntegrations (between two systems): Use when someone asks what CRM Connector can do, which integrations or systems it offers or supports, whether it can connect a business system, which systems it pairs with, or what travels between two…
get_field_detailsIntegrations (between two systems): Use when someone asks whether a particular field travels between two systems for one record type, for example the phone number, the address, the due date, the line items or the tax of an invoice…
get_connection_guideIntegrations (between two systems): Use when someone asks how to connect a system to CRM Connector, what they need for it (an api key, a token, an account id, a store address) or where to find it, or whether connecting means signing in or…
list_integrationsIntegrations (between two systems): Use when a signed in CRM Connector customer asks about their own integrations, and only then: which ones they set up, whether they are running, or when they last synced. Returns each integration with…
run_syncIntegrations (between two systems): Use when a signed in CRM Connector customer wants one of their integrations to sync now, for example after fixing what made records fail. mode changes (the default) picks up what changed since the last…
set_integration_statusIntegrations (between two systems): Use when a signed in CRM Connector customer wants one of their integrations paused (nothing syncs, nothing is deleted) or running again (status active, which also switches on a draft once the account…
get_sync_healthIntegrations (between two systems): Use when a signed in CRM Connector customer asks how their syncs are doing: what failed, why records did not arrive, what is waiting, when an integration last ran or which conflicts wait for a choice…
resolve_conflictIntegrations (between two systems): Use after get_sync_health with include conflicts, once the person chose. choice sync makes the record that also matches the one the shared record follows from the next sync; choice keep_apart leaves…
get_ai_agents_infoAI Agents (inside one system): Use when someone asks about connecting one of their business systems to ChatGPT and Claude so the assistant works with its records itself: reading or searching customers, deals, invoices or quotes, changing…
list_ai_systemsAI Agents (inside one system): Use first when a signed in CRM Connector customer asks about the records in their own business systems (contacts, deals, invoices and so on). Returns the systems they connected to AI Agents, each with its…
describe_record_typeAI Agents (inside one system): Use before searching or changing records of one type in an AI agent's system: everything about the type in one answer. Returns the fields CRM Connector reads the same way in every system (fields: which may…
search_recordsAI Agents (inside one system): Use to find records of one type in an AI agent's system, page by page. Search with text for the system's own search (contacts by name, email or phone, deals by name, invoices by number; leave it out to page…
get_recordAI Agents (inside one system): Use to read one record of an AI agent's system by its id, live from the system. Returns the fields CRM Connector reads the same way in every system; add fields to read some of the system's own fields as…
find_linked_recordsAI Agents (inside one system): Use for questions across systems, such as which won deals have no invoice in the books yet or which contact is which customer: for up to 50 records of one system it returns the same records in the customer's…
list_related_recordsAI Agents (inside one system): Use to see which records of another type, or which notes, tasks, calls, meetings or emails, one record is linked to inside an AI agent's system, such as the deals of a contact or the notes of a deal. Not for…
read_activitiesAI Agents (inside one system): Use to read notes, tasks, calls, meetings or emails of an AI agent's system by their ids, as list_related_records gives them. Not for finding them (use list_related_records first). Their content is the…
list_changesAI Agents (inside one system): Use when the customer asks what the assistant changed in their systems, or to find a change to undo. Returns the newest proposed, applied, failed and undone changes, each with its before and after values and…
propose_changesAI Agents (inside one system): Use whenever the person asks to change records in a system whose AI agent may change them: every change goes through here first, and nothing is written. Pick one action and give one item per record, at most…
apply_proposalAI Agents (inside one system): Use only after the customer saw the changes of a proposal and said yes. It writes exactly what one proposal of propose_changes showed, and nothing else. CRM Connector reads every record again, refuses one…
undo_changeAI Agents (inside one system): Use when the customer asks to undo a change the assistant made. It puts the values from before back, only while the record still holds what was written, so newer work is never overwritten. A new record…
propose_automationAI Agents (inside one system): Use when the customer wants something to keep happening by itself inside one system on AI Agent (not for a one-off change: use propose_changes), such as "when a deal is won and the amount is above 5,000, add…
list_automationsAI Agents (inside one system): Use when the customer asks which automations run in their system, whether a rule ran, or to find one to pause, resume, change or remove. Returns each rule as a sentence (when, only if, then) with its id…
set_automation_statusAI Agents (inside one system): Use when the customer asks to pause, resume or remove one automation, after they confirmed. pause stops it until it is resumed; resume switches a paused rule on again, and a rule the customer never approved…
send_requestIntegrations and AI Agents: Use when the person wants something CRM Connector does not offer yet, to ask for it for them, for either product: an integration with a system it does not connect yet (kind integration), or AI Agents set up for…
get_profileIntegrations and AI Agents: Use when you need to know which CRM Connector account is connected, for example right after connecting or to tell two connected accounts apart. Returns an opaque id, the organisation name and the email address…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"crm-connector": {
"type": "http",
"url": "https://platform-mcp.crm-connector.com"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http crm-connector https://platform-mcp.crm-connector.comclaude.ai, ChatGPT and other clients: add https://platform-mcp.crm-connector.com as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.