Servidor MCP de CRM Connector

• Nombre en el registrocom.crm-connector/crm-connectorverificado en el registro MCP

El nombre en el registro está bajo crm-connector.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-29
• Herramientas26
• El servidor se llamacrm-connector
• Versión del servidor1.1.1
• Versión del protocolo2025-06-18

El 2026-10-29 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 260 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 5 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 5 hasta ahora
• Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta215 ms
• Espacio en el contexto del agente≈ 14.038 tokenslas definiciones de todas sus herramientas (30), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados30 de 30 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• plan_integration

  Integrations (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_options

  Integrations (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_details

  Integrations (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_guide

  Integrations (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_integrations

  Integrations (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_sync

  Integrations (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_status

  Integrations (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_health

  Integrations (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_conflict

  Integrations (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_info

  AI 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_systems

  AI 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_type

  AI 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_records

  AI 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_record

  AI 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_records

  AI 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_records

  AI 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_activities

  AI 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_changes

  AI 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_changes

  AI 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_proposal

  AI 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_change

  AI 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_automation

  AI 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_automations

  AI 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_status

  AI 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_request

  Integrations 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_profile

  Integrations 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…