Relm MCP server
Which servers in the official MCP registry are Relm's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry namecom.relmcrm/relmverified in the MCP registry
The registry name sits under relmcrm.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools41
- Server calls itselfrelm
- Server version0.17.1
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 652 ms.
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer722 ms
- Space in an agent's context≈ 3,910 tokensthe definitions of all its tools (41), which an agent carries on every turn
- Tool definitionsB · 87 of 100
- Parameters without a description: in 32 of 41
Worth a look
- Tools that change data, on a server that answers without a sign-in: relm_create, relm_update, relm_delete, relm_create_pipeline, relm_create_type
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 state of vendors' MCP servers: method and numbers →
relm_describe_schemaReturn 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_searchCross-entity search over contacts, companies and deals by name/email/title.
relm_listList 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_getFetch one record by id.
relm_createCreate 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_updatePatch a record. Pass if_match (the record's current version) for optimistic concurrency; a 412 means re-fetch and retry.
relm_deleteSoft-delete a record (recoverable via relm_restore). Never hard-destroys data.
relm_restoreRestore a soft-deleted record.
relm_log_activityLog an activity (note/call/email/meeting/task) on a contact and/or deal. Convenience wrapper over create activity.
relm_list_pipelinesList pipelines with their ordered stages.
relm_create_pipelineCreate a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.
relm_manage_stageAdd, 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_typeRegister a new object type in the schema (registry). Idempotent on key; returns the full type set.
relm_create_fieldRegister 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_valueAdd 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_batchRun 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_capabilitiesDiscover 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_channelConnect 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_connectionsList connected messaging channels (never returns the secret key).
relm_create_automationCreate 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_automationsList reactive rules (automations).
relm_create_templateCreate 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_templatesList reusable email templates.
relm_create_sequenceCreate 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_sequencesList drip sequences with their steps and enrollment counts.
relm_preview_sequenceDry-run a sequence: how many contacts would enroll now + the send schedule. No side effects.
relm_enrollManually 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_webhookSubscribe 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_webhooksList webhook subscriptions in this workspace/mode.
relm_delete_webhookDelete a webhook subscription by id.
relm_get_automationRead one automation by id, with its trigger, conditions and actions.
relm_get_sequenceRead one drip sequence by id. view=sequence (default) returns it with its steps; view=enrollments lists who is enrolled and their state.
relm_get_pipelineRead one pipeline by key or pl_ id, with its ordered stages and their semantic types (open/won/lost).
relm_get_webhookRead 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_automationChange 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_sequenceChange 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_pipelineChange 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_webhookPause 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_connectionDelete a connected messaging channel by id (e.g. to remove a rotated/wrong Resend key).
relm_get_usageRead 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_capSet (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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"relm": {
"type": "http",
"url": "https://api.relmcrm.com/mcp"
}
}
}OpenAPI spec
41 paths, read 2026-10-20. Open the spec ↗
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.