Skip to main content
Glama
RD Station CRM MCP

RD Station CRM MCP

rdstation-crm-mcp

CI npm version License: MIT

An open-source MCP server for RD Station CRM — the leading CRM in Brazil and Latin America. Manage contacts, deals, tasks and notes, and get pipeline health reports, straight from Claude or any MCP-compatible client.

"How's my sales pipeline this month?" → stage-by-stage totals, win rate, and the deals going stale.

Demo: connecting to the server and running rdcrm_pipeline_overview against a real RD Station CRM account

Why

RD Station CRM is huge in the LatAm market, but had no open-source MCP server. This project connects it to the MCP ecosystem so AI agents can work your pipeline: qualifying leads, moving deals, scheduling follow-ups, and answering questions about your sales data in natural language.

Related MCP server: Salesmate MCP Server

Quick start

  1. Get your instance token in RD Station CRM: Profile → Products and integrations → Instance token.

  2. Add the server to your MCP client.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "rdstation-crm": {
      "command": "npx",
      "args": ["-y", "rdstation-crm-mcp"],
      "env": {
        "RDSTATION_CRM_TOKEN": "your-instance-token"
      }
    }
  }
}

Claude Code:

claude mcp add rdstation-crm -e RDSTATION_CRM_TOKEN=your-instance-token -- npx -y rdstation-crm-mcp

That's it. Ask Claude something like "list my open deals" or "give me a pipeline overview".

Tools

Tool

Description

rdcrm_search_contacts

Search contacts by name, email or phone

rdcrm_get_contact

Contact details, including linked deals

rdcrm_upsert_contact

Create a contact, or update it if the email already exists

rdcrm_list_deals

List deals filtered by status, pipeline, stage, owner, dates

rdcrm_get_deal

Deal details: stage, value, owner, contacts, products

rdcrm_create_deal

Create a deal — accepts stage by name, resolved automatically

rdcrm_update_deal

Move stage, change owner, rating, close date, pause/resume

rdcrm_close_deal

Mark won or lost (lost reasons resolved by name)

rdcrm_list_tasks

List tasks by deal, assignee, status, type, due date

rdcrm_create_task

Create a task (call, email, meeting, whatsapp...) on a deal

rdcrm_add_note

Add a note to a deal's timeline

rdcrm_pipeline_overview

Pipeline health report: totals per stage, win rate, stalled deals

Design notes

These tools are designed for LLMs, not as a 1:1 API wrapper:

  • Names instead of IDs. Stages, pipelines, users and lost reasons can be passed by name; the server resolves them against the account and lists the valid options when something doesn't match.

  • Compact responses. List tools return one line per record with the fields that matter, plus explicit pagination hints. Large responses are truncated with guidance instead of flooding the context window.

  • Actionable errors. A 401 tells you which env var to check; an unknown stage lists every stage in every pipeline.

  • Aggregation where it counts. rdcrm_pipeline_overview answers the questions humans actually ask ("where are deals stuck?") with a single tool call.

Remote deployments (Streamable HTTP)

The default (rdstation-crm-mcp) runs over stdio for a single local user, with the token read once from RDSTATION_CRM_TOKEN. For a team-hosted or registry-listed deployment (e.g. Smithery), run the Streamable HTTP variant instead:

npx -y rdstation-crm-mcp-http

This starts an HTTP server (http://127.0.0.1:8080/mcp by default) implementing the MCP Streamable HTTP transport, with proper session lifecycle (initialize → Mcp-Session-Id → DELETE to close).

Because a hosted server can serve more than one user, there's no single implicit token: each session sends its own Authorization: Bearer <token> header on initialize. A RDSTATION_CRM_TOKEN env var still works as a fallback default for a single-tenant self-hosted setup where every caller shares one CRM account.

Env vars:

Var

Default

Purpose

PORT

8080

Port to listen on

HOST

127.0.0.1

Bind address — use 0.0.0.0 for containers/cloud

ALLOWED_HOSTS

(unset)

Comma-separated Host header allow-list (DNS-rebinding guard); recommended when binding to 0.0.0.0 without a reverse proxy in front

RDSTATION_CRM_TOKEN

(unset)

Default token used when a session sends no Authorization header

curl http://127.0.0.1:8080/health
# {"status":"ok","server":"rdstation-crm-mcp","sessions":0}

Development

git clone https://github.com/fernandoludvig/rdstation-crm-mcp.git
cd rdstation-crm-mcp
npm install
npm test              # unit tests (API mocked with msw)
npm run typecheck
npm run build
RDSTATION_CRM_TOKEN=xxx npx @modelcontextprotocol/inspector node dist/index.js

The HTTP layer (src/client/) is isolated from the tools, with retry and exponential backoff for 429/5xx built in.

Roadmap

  • Organizations and products tools

  • RD Station CRM API v2 support (OAuth) behind the same tool surface

  • Streamable HTTP transport for remote deployments

  • Publish to MCP registries (Glama, PulseMCP, Smithery)

Contributions welcome — open an issue first for anything non-trivial.

License

MIT © Fernando Ludvig

Not affiliated with or endorsed by RD Station. Uses the public RD Station CRM API v1.

Available Tools

12 tools
rdcrm_add_noteAdd Note to RD Station CRM DealA

Add a text note (annotation) to a deal's timeline.

The author can be given by user_id, by email/name in 'user', or omitted when the account has a single user.

Use when: "note on the Acme deal: client asked for a discount".

Inputs: text (required), deal_id (required), user, user_id.

rdcrm_close_dealClose RD Station CRM Deal (Won/Lost)A

Mark a deal as won or lost. For lost deals, pass the reason by name (lost_reason) or ID (lost_reason_id) — names are resolved against the reasons configured in the account — plus an optional note.

Use when: "mark the Acme deal as won", "we lost the Beta deal because of price".

Inputs: deal_id (required), outcome (required), note, lost_reason, +1 more.

rdcrm_create_dealCreate RD Station CRM DealA

Create a deal in a pipeline stage. Accepts the stage by ID or by name (stage_name, optionally with pipeline_name to disambiguate) — names are resolved automatically.

Optional: value (BRL), rating (1-5), owner (user_id or user by email/name), a contact to link (contact_email + contact_name), expected close date.

Use when: "create a deal for Acme in the Qualification stage worth R$5000".

Inputs: name (required), user, value, rating, +7 more.

rdcrm_create_taskCreate RD Station CRM TaskA

Create a task on a deal: subject, type (call, email, meeting, task, lunch, visit, whatsapp), due date and time, assignee. Note: free-plan accounts only allow type 'task'; other types return a 403 (paid feature).

The assignee can be given by user_id, by email/name in 'user' (resolved automatically), or omitted when the account has a single user.

Use when: "schedule a follow-up call on the Acme deal for Friday 10am".

Inputs: date (required), deal_id (required), subject (required), hour, +4 more.

rdcrm_get_contactGet RD Station CRM ContactA
Read-only

Get full details of one contact by ID: all emails and phones, title, notes, and the deals linked to the contact with their status (open/won/lost).

Get the contact ID from rdcrm_search_contacts first.

Inputs: contact_id (required).

rdcrm_get_dealGet RD Station CRM DealA
Read-only

Get full details of one deal by ID: status, stage, value, owner, rating, dates, linked contacts (with email/phone) and products.

Inputs: deal_id (required).

rdcrm_list_dealsList RD Station CRM DealsA
Read-only

List deals with filters: status (open/won/lost/all, default open), pipeline, stage, owner, name, creation date range. Sorted by most recent first.

Returns one line per deal: name, id, stage, value, status, owner, last update. Use rdcrm_get_deal for full details.

Use when: "what deals are open?", "deals lost this month", "show João's pipeline".

Inputs: name, page, limit, status, +5 more.

rdcrm_list_tasksList RD Station CRM TasksA
Read-only

List tasks with filters: deal, assignee, status (pending/done/all, default pending), type (call, email, meeting, task, lunch, visit, whatsapp) and due-date range.

Returns one line per task: status, subject, id, type, due date, assignee, deal.

Use when: "what are my pending tasks?", "overdue follow-ups this week".

Inputs: page, type, limit, status, +4 more.

rdcrm_pipeline_overviewRD Station CRM Pipeline OverviewA
Read-only

Aggregated health report of a sales pipeline: open deal count and value per stage (in funnel order), won/lost counts and win rate over a recent window (default 30 days), and stalled deals with no updates for N days (default 14).

Also the fastest way to discover the account's pipelines and stage names/IDs (errors list all options).

Use when: "how's my pipeline?", "where are deals stuck?", "sales summary for this month".

Inputs: stalled_days, pipeline_name, closed_period_days.

rdcrm_search_contactsSearch RD Station CRM ContactsA
Read-only

Search contacts in RD Station CRM by partial name, exact email or exact phone.

Returns one line per contact: name, id, primary email, primary phone, job title. Use the returned id with rdcrm_get_contact for full details (including linked deals).

Use when: "find Maria's contact", "do we have someone with email x@y.com?". Don't use when: you want to create or edit a contact (use rdcrm_upsert_contact).

Inputs: page, email, limit, phone, +1 more.

rdcrm_update_dealUpdate RD Station CRM DealA

Update a deal: move it to another stage (by ID or name), change owner, rename, set rating, expected close date, or pause/resume (hold).

Use when: "move the Acme deal to Negotiation", "assign this deal to Maria". Don't use when: marking a deal won or lost (use rdcrm_close_deal).

Inputs: deal_id (required), hold, name, user, +6 more.

rdcrm_upsert_contactCreate or Update RD Station CRM ContactA
Idempotent

Create a contact, or update it if one already exists with the given email (matched by exact email).

Provide at least email and name. Phone, job title and notes are optional. Returns the contact id.

Use when: "add João (joao@acme.com) to the CRM", "update Maria's phone".

Inputs: name (required), email (required), notes, phone, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action combination: search/get/upsert for contacts, list/get/create/update/close for deals, list/create for tasks, add for notes, and overview for reporting. There is no overlap—rdcrm_get_contact vs rdcrm_get_deal are clearly separated by resource, and update_deal explicitly defers close operations to close_deal, preventing confusion.

    Naming Consistency4/5

    The tools follow a highly consistent rdcrm_<resource>_<verb> pattern (rdcrm_search_contacts, rdcrm_get_deal, rdcrm_create_task) throughout. The only minor deviation is rdcrm_pipeline_overview and rdcrm_add_note, which use different verb styles (overview vs get/list, add vs create) rather than strictly following the verb_noun pattern.

    Tool Count5/5

    12 tools is well within the sweet spot for a CRM server covering contacts, deals, tasks, notes, and pipeline reporting. Each tool serves a clearly identifiable purpose in the sales workflow, and none feel redundant. The count feels right-sized for the domain.

    Completeness4/5

    The surface covers the full contact lifecycle (search/get/upsert), the deal lifecycle (list/get/create/update/close), plus tasks, notes, and pipeline analytics—strong coverage. Minor gaps exist: there is no tool to delete a contact or task, no tool to update a task (e.g., mark done), and no way to unlink a contact from a deal. These are workable gaps, not dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Pipedrive API v2, enabling management of deals, persons, organizations, products, activities, and pipelines through natural language in MCP clients like Cursor and Claude Desktop.
      12 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A production-ready MCP server that exposes the Salesmate CRM to Claude Desktop, enabling search, update, and creation of contacts, deals, tasks, notes, and activities.
      8
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that connects a Follow Up Boss CRM account to Claude, enabling CRM operations through natural language via 25 curated tools and a raw API tool.
      -