
Servidor MCP de CRM Connector
Quais servidores MCP são de CRM Connector, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.
lido em 2026-10-29
- Nome no registrocom.crm-connector/crm-connectorverificado no registro MCP
O nome no registro fica sob crm-connector.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.
- Estadorespondeverificado em 2026-10-29
- Ferramentas26
- O servidor se chamacrm-connector
- Versão do servidor1.1.1
- Versão do protocolo2025-06-18
Em 2026-10-29 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 260 ms.
- Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
- Verificado em 5 dos 7 dias necessários para julgar a confiabilidade.
Depois de conectar
- Mantenha a aprovação para send_request: elas apagam, enviam ou pagam sem avisar.
- send_request alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.
- Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 5 até agora
- Respondeumedindo5 das 7 verificações diárias necessárias para mostrar a porcentagem
- Mediana da primeira resposta215 ms
- Espaço no contexto do agente≈ 14.038 tokensas definições de todas as ferramentas (30), que o agente carrega a cada turno
- Definições das ferramentasA · 100 de 100
- Resultados tipados30 de 30 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
- Todas as ferramentas passam nas seis verificações.
O que um agente consegue fazer com ele
- incerto · sync customers and invoices between GoHighLevel and accounting tools
- incerto · push field service appointments and jobs into GoHighLevel
- incerto · link contacts from HubSpot or Salesforce into GoHighLevel
Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?
Vale conferir
- Ferramentas que apagam, enviam ou pagam, marcadas como não destrutivas: send_request
- Ferramentas que alteram dados, em um servidor que responde sem login: send_request
Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →
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…
Como conectar
Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:
{
"mcpServers": {
"crm-connector": {
"type": "http",
"url": "https://platform-mcp.crm-connector.com"
}
}
}Adicionar
Claude Code, no terminal
claude mcp add --transport http crm-connector https://platform-mcp.crm-connector.comAdicionar ao CursorAdicionar ao VS Code
claude.ai, ChatGPT e outros clientes: adicione https://platform-mcp.crm-connector.com como conector personalizado nas configurações.
Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.
Antes de contar esta visita
A análise e a medição de anúncios nos dizem quais páginas e quais dos nossos anúncios cumprem seu papel: Google Analytics e Google Ads, o pixel da Meta, Yandex Metrica e um identificador próprio. Nada é armazenado até você responder, e recusar não muda nada no site.