mcp server
Relm CRM
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Description as published by the maintainer. Source
- version 0.10.0
- active
active — Registry entry last updated 2026-07-24.
What this server can do
41 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
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(operations)- 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). Required: operations.
relm_connect_channel(from, name, api_key, channel, provider)- 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. Required: api_key.
relm_create(data, object)- 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. Required: object, data.
relm_create_automation(name, actions, enabled, conditions, trigger_event)- 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. Required: name, trigger_event, actions.
relm_create_enum_value(group, label, 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. Required: group, value.
relm_create_field(key, label, object, required, data_type, enum_group)- 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. Required: object, key.
relm_create_pipeline(key, name, stages, is_default)- Create a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.
relm_create_sequence(name, steps, channel, enabled, trigger, exit_when, connection, enroll_existing)- 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'. Required: name, steps.
relm_create_template(key, html, name, text, subject)- 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>"}. Required: name, html.
relm_create_type(key, label)- Register a new object type in the schema (registry). Idempotent on key; returns the full type set. Required: key.
relm_create_webhook(url, events, enabled, description)- 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. Required: url.
relm_delete(id, object)- Soft-delete a record (recoverable via relm_restore). Never hard-destroys data. Required: object, id.
relm_delete_connection(id)- Delete a connected messaging channel by id (e.g. to remove a rotated/wrong Resend key). Required: id.
relm_delete_webhook(id)- Delete a webhook subscription by id. Required: 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(source, contact_id, sequence_id)- Manually enroll a contact into a sequence (idempotent per contact+sequence). Optional source={object,id} records what drove the enrollment (e.g. a deal). Required: sequence_id, contact_id.
relm_get(id, object)- Fetch one record by id. Required: object, id.
relm_get_automation(id)- Read one automation by id, with its trigger, conditions and actions. Required: id.
relm_get_pipeline(pipeline)- Read one pipeline by key or pl_ id, with its ordered stages and their semantic types (open/won/lost). Required: pipeline.
relm_get_sequence(id, view)- Read one drip sequence by id. view=sequence (default) returns it with its steps; view=enrollments lists who is enrolled and their state. Required: id.
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(id, view)- 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. Required: id.
relm_list(limit, cursor, filter, object)- 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). Required: object.
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(body, type, deal_id, contact_id)- Log an activity (note/call/email/meeting/task) on a contact and/or deal. Convenience wrapper over create activity.
relm_manage_automation(id, action)- 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. Required: id, action.
relm_manage_pipeline(name, action, new_key, 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. Required: pipeline, action.
relm_manage_sequence(id, action)- 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. Required: id, action.
relm_manage_stage(key, type, label, order, action, new_key, ordinal, pipeline)- 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. Required: pipeline, action.
relm_manage_webhook(id, action)- 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. Required: id, action.
relm_preview_sequence(id)- Dry-run a sequence: how many contacts would enroll now + the send schedule. No side effects. Required: id.
relm_restore(id, object)- Restore a soft-deleted record. Required: object, id.
relm_search(limit, query)- Cross-entity search over contacts, companies and deals by name/email/title. Required: query.
relm_set_spend_cap(overage_cap_usd)- 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. Required: overage_cap_usd.
relm_update(id, patch, object, if_match)- Patch a record. Pass if_match (the record's current version) for optimistic concurrency; a 412 means re-fetch and retry. Required: object, id, patch.
Last successful function declaration observed on . Source: https://api.relmcrm.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.relmcrm.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.10.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 41 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.relmcrm.com | |
| mcp endpoint status | ok | The server listed 41 functions when asked. | as of probe | api.relmcrm.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json