Servidor MCP de Relm

• Nombre en el registrocom.relmcrm/relmverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-20
• Herramientas41
• El servidor se llamarelm
• Versión del servidor0.17.1
• Versión del protocolo2025-06-18

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

• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta722 ms
• Espacio en el contexto del agente≈ 3910 tokenslas definiciones de todas sus herramientas (41), que el agente lleva en cada turno
• Definiciones de herramientasB · 87 de 100

• Parámetros sin descripción: en 32 de 41

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. El estado de los servidores MCP de los proveedores: método y números →

• relm_describe_schema

  Return the live schema: every object, its fields (built-in + custom), and all enum groups with their current values (contact types, activity types, etc). ALWAYS call this before guessing a type, stage, or field - it is the source of truth…

• relm_search

  Cross-entity search over contacts, companies and deals by name/email/title.

• relm_list

  List records of an object with keyset pagination. Optional filters vary by object (e.g. contact: email/company_id/type; deal: pipeline/stage/company_id; activity: contact_id/deal_id/type).

• relm_get

  Fetch one record by id.

• relm_create

  Create a record. `data` is the object's fields (see relm_describe_schema). Custom fields must be registered first (relm_create_field). A contact needs at least one of: a name, an identifier (email/phone/linkedin_url), a company, or a…

• relm_update

  Patch a record. Pass if_match (the record's current version) for optimistic concurrency; a 412 means re-fetch and retry.

• relm_delete

  Soft-delete a record (recoverable via relm_restore). Never hard-destroys data.

• relm_restore

  Restore a soft-deleted record.

• relm_log_activity

  Log an activity (note/call/email/meeting/task) on a contact and/or deal. Convenience wrapper over create activity.

• relm_list_pipelines

  List pipelines with their ordered stages.

• relm_create_pipeline

  Create a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.

• relm_manage_stage

  Add, rename/retype, delete, or reorder stages in a pipeline. action=add: `key` (+optional label, ordinal, type). action=rename: `key` (existing) + any of new_key / label / type - keys are slugified and deals follow automatically (fixes a…

• relm_create_type

  Register a new object type in the schema (registry). Idempotent on key; returns the full type set.

• relm_create_field

  Register a new custom field on an object (contact/company/deal/activity). data_type: text|number|boolean|date|select|multiselect|currency|reference|email|url. Must be created before it can be written to a record.

• relm_create_enum_value

  Add a value to an enum group (e.g. group 'contact.type' value 'partner'). Idempotent; returns the full value set. Use this when relm_create rejects an unknown type with a valid_options list.

• relm_batch

  Run up to 100 record writes in ONE call (contact/company/deal/activity) - the fast path for imports/migrations. operations: [{object, method:create|update|delete, data|patch, id?}]. Returns a per-op result array (partial success). Every…

• relm_automations_capabilities

  Discover the automation building blocks: valid trigger_events, condition ops, action types, channels/providers, and the shapes of automations/sequences/connections. Call before building a rule or sequence.

• relm_connect_channel

  Connect a BYO messaging channel so automations can send. channel='email', provider='resend', api_key=<your Resend key>, from='Team <hi@you.com>' (must be a verified Resend sender). The key is encrypted at rest.

• relm_list_connections

  List connected messaging channels (never returns the secret key).

• relm_create_automation

  Create a single-step rule: when <trigger_event> [if <conditions>] then <actions>. conditions=[{field,op,value}] (ANDed), actions=[{type,...}]. Example: trigger_event='deal.stage_changed', conditions=[{field:'stage',op:'eq',value:'won'}]…

• relm_list_automations

  List reactive rules (automations).

• relm_create_template

  Create a reusable email template. name, html (full HTML, {{field}} placeholders ok), optional subject + text (plaintext alt; auto-derived if omitted). Reference it from a rule/sequence step via {"type":"send_email","template":"<key or…

• relm_list_templates

  List reusable email templates.

• relm_create_sequence

  Create a multi-step drip sequence. trigger={event,filter:[{field,op,value}]} auto-enrolls the matching entity's contact; exit_when=[{field,op,value}] stops it (re-checked before every send); steps=[{wait_days,subject,body}] (first step…

• relm_list_sequences

  List drip sequences with their steps and enrollment counts.

• relm_preview_sequence

  Dry-run a sequence: how many contacts would enroll now + the send schedule. No side effects.

• relm_enroll

  Manually enroll a contact into a sequence (idempotent per contact+sequence). Optional source={object,id} records what drove the enrollment (e.g. a deal).

• relm_create_webhook

  Subscribe an https endpoint to CRM events. events=['*'] for all, or a subset of ['contact.created','contact.updated','deal.created','deal.updated','deal.stage_changed']. Returns a `secret` ONCE - the subscriber verifies the…

• relm_list_webhooks

  List webhook subscriptions in this workspace/mode.

• relm_delete_webhook

  Delete a webhook subscription by id.

• relm_get_automation

  Read one automation by id, with its trigger, conditions and actions.

• relm_get_sequence

  Read one drip sequence by id. view=sequence (default) returns it with its steps; view=enrollments lists who is enrolled and their state.

• relm_get_pipeline

  Read one pipeline by key or pl_ id, with its ordered stages and their semantic types (open/won/lost).

• relm_get_webhook

  Read one webhook by id. view=webhook (default) returns the subscription; view=deliveries returns recent delivery attempts (status, retries, dead-letter) to debug why an endpoint isn't receiving events.

• relm_manage_automation

  Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's…

• relm_manage_sequence

  Change an existing drip sequence by id. action=disable stops further sends (use this to halt a bad sequence); action=enable resumes; action=delete removes it. To read one or list its enrollments, use relm_get_sequence.

• relm_manage_pipeline

  Change an existing pipeline by key or pl_ id. action=rename changes its display `name` and/or its key (pass `new_key`) - deals link by internal id, so they follow a re-key automatically; action=set_default makes it the workspace default…

• relm_manage_webhook

  Pause or resume delivery for an existing webhook by id. action=enable/disable. To read one or inspect its delivery attempts, use relm_get_webhook. To remove it, use relm_delete_webhook.

• relm_delete_connection

  Delete a connected messaging channel by id (e.g. to remove a rotated/wrong Resend key).

• relm_get_usage

  Read this workspace's current billing period: requests used, plan, monthly limit, and any metered overage. Call this to see how close you are to the quota before a big import.

• relm_set_spend_cap

  Set (or clear) the hard monthly overage spend cap in USD. overage_cap_usd: a number caps paid overage (requests 429 with spend_cap_reached past it), 0 = never any overage, null = unlimited. This is the recovery for a spend_cap_reached…