mcpbeat

Relm CRM MCP Server

com.relmcrm/relm
answering

Relm CRM is answering right now. Last checked 3 min ago. It exposes 41 tools.

API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
92 of 92 checks
41
Tools
read from the server
118 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add relm --transport http https://api.relmcrm.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "relm": {
      "url": "https://api.relmcrm.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.relm]
url = "https://api.relmcrm.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "relm": {
      "url": "https://api.relmcrm.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "relm": {
      "url": "https://api.relmcrm.com/mcp"
    }
  }
}

Available tools 41

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

relm
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_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 op still counts against your quota (batch saves round-trips, not quota).
relm_connect_channel
Connect a BYO messaging channel so automations can send. channel='email', provider='resend', api_key=<your Resend key>, from='Team <[email protected]>' (must be a verified Resend sender). The key is encrypted at rest.
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 custom field (email is unique per workspace) - don't invent a placeholder email.
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'}], actions=[{type:'create_activity',body:'Deal won!'}]. See relm_automations_capabilities.
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_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_pipeline
Create a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.
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 wait_days:0 sends now). enroll_existing:true also enrolls everything that currently matches. Example: 3 emails to contacts of deals entering stage 'lead', stop if the deal leaves 'lead'.
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 tmpl_id>"}.
relm_create_type
Register a new object type in the schema (registry). Idempotent on key; returns the full type set.
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-Signature` header (t=<unix>,v1=<hmac-sha256 of "t.body">). Deliveries retry with backoff and dead-letter after 6 attempts.
relm_delete
Soft-delete a record (recoverable via relm_restore). Never hard-destroys data.
relm_delete_connection
Delete a connected messaging channel by id (e.g. to remove a rotated/wrong Resend key).
relm_delete_webhook
Delete a webhook subscription by id.
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 for what exists.
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_get
Fetch one record by id.
relm_get_automation
Read one automation by id, with its trigger, conditions and actions.
relm_get_pipeline
Read one pipeline by key or pl_ id, with its ordered stages and their semantic types (open/won/lost).
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_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_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_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_list_automations
List reactive rules (automations).
relm_list_connections
List connected messaging channels (never returns the secret key).
relm_list_pipelines
List pipelines with their ordered stages.
relm_list_sequences
List drip sequences with their steps and enrollment counts.
relm_list_templates
List reusable email templates.
relm_list_webhooks
List webhook subscriptions in this workspace/mode.
relm_log_activity
Log an activity (note/call/email/meeting/task) on a contact and/or deal. Convenience wrapper over create activity.
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 trigger/conditions/actions, delete and recreate.
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; action=delete removes it (fails if deals still use it - move them first). To read one, use relm_get_pipeline.
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_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 typo'd key). action=delete: `key` (a stage in use by deals cannot be deleted). action=reorder: `order` = every existing stage key exactly once, in the new order. `type` is the semantic stage type: open | won | lost - so 'is this deal won?' is a flag (stage_type on every deal), not per-pipeline string matching.
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_preview_sequence
Dry-run a sequence: how many contacts would enroll now + the send schedule. No side effects.
relm_restore
Restore a soft-deleted record.
relm_search
Cross-entity search over contacts, companies and deals by name/email/title.
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 error.
relm_update
Patch a record. Pass if_match (the record's current version) for optimistic concurrency; a 412 means re-fetch and retry.

Endpoints

URLTransportStateLatencyChecked
https://api.relmcrm.com/mcp streamable-http answering 150 ms 3 min ago

Relm CRM — questions

Answers built from our own checks of this server.

What can Relm CRM do?
It exposes 41 tools, read directly from the server on our last check. Among them: relm_automations_capabilities, relm_batch, relm_connect_channel, relm_create, relm_create_automation, relm_create_enum_value and 35 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Relm CRM working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 118 ms. The bar chart above shows every period we have measured.
How do I connect Relm CRM?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Relm CRM need an API key?
No. Relm CRM completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 41 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Relm CRM?
It answers our handshake in 118 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.