List your agent

Relm CRM

MCP server● Hosted · onlinev0.17.1

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: enrich CRM contacts.
All AI agents to enrich CRM contacts, ranked →

Similar tools

Listed for the same task: enrich CRM contacts

Reviews

No review yet. Used Relm CRM? Be the first to help others choose.

What it does

Relm CRM is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: crm integration. That makes it a candidate for tasks such as enrich CRM contacts or follow up on quotes.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.17.1
PriceNot in the registry
First seen26 Sept 2026
Last checked5d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 22h ago (live check)

Hosted endpoint

  • https://api.relmcrm.com/mcp streamable-http

In Claude Code: claude mcp add --transport http relm-crm https://api.relmcrm.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "relm-crm": {
      "url": "https://api.relmcrm.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 22h ago

ONLINE Relm CRM answered an MCP connection on 14 Nov 2026 and introduced itself as relm 0.17.1 (MCP protocol 2025-06-18).

41 tools offered to AI assistants

  • 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 f
  • 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 custom
  • 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 ty
Show 29 more
  • 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 op
  • 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'}], ac
  • 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 tmpl_
  • 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 wait
  • 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-Signature`
  • 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 trigger/conditions/a
  • 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; ac
  • 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 error

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.relmcrm.com/mcpDECLAREDSRC-001 Official MCP Registry5d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry5d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry5d ago
Websitehttps://relmcrm.com/DECLAREDSRC-001 Official MCP Registry5d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry5d ago
Version0.17.1DECLAREDSRC-001 Official MCP Registry5d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry5d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Relm CRM? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Relm CRMLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Relm CRM?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/relm-crm?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/relm-crm/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Relm CRM

How do I connect Relm CRM?

Use the hosted endpoint https://api.relmcrm.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Relm CRM offer?

When Electra Index connected on 14 Nov 2026, it listed 41 tools: relm_describe_schema, relm_search, relm_list, relm_get, relm_create, relm_update, relm_delete, relm_restore and more. The full list is in "Live check" above.

Is Relm CRM online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 22h ago.

What can I use Relm CRM for?

Based on its description, it is most relevant to: enrich CRM contacts, follow up on quotes, update the CRM after calls, forecast sales pipeline.