rd-station-crm
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rd-station-crm list my deals in the sales pipeline"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
conectar-rd-station-mcp
Servidor MCP (Model Context Protocol) local que expõe ferramentas do RD Station CRM (contatos, organizações, negócios/deals, pipelines, usuários) para clientes MCP como Claude Code e Codex CLI.
Roda via stdio — o cliente (Claude/Codex) inicia o processo sozinho quando precisa, não é um servidor que fica no ar o tempo todo.
Pré-requisitos
Um token de API do RD Station CRM (Configurações → Integrações → API na sua conta RD Station)
Claude Code e/ou Codex CLI instalados, se quiser o registro automático
Não precisa ter o Node.js instalado antes — o script de setup verifica e instala uma versão compatível (18+) via nvm se necessário.
Related MCP server: HubSpot CRM MCP Server
Instalação rápida
npm run setup(se ainda não tiver npm/Node, rode bash scripts/setup.sh direto)
Isso vai:
Checar se o Node.js 18+ está instalado — se não estiver (ou for uma versão antiga), instala via nvm automaticamente
Instalar as dependências (
npm install)Buildar o projeto (
npm run build)Criar o arquivo
.env(a partir de.env.example) e pedir seu token do RD StationRegistrar o servidor como
rd-station-crmno Claude Code e no Codex CLI, se encontrar os dois instalados na máquina
Instalação manual (passo a passo)
Se preferir fazer na mão, ou se o script não encontrar o Claude/Codex automaticamente:
Instale as dependências e builde
npm install npm run buildConfigure o token
cp .env.example .envAbra o
.enve preencha:RD_STATION_TOKEN=seu_token_aquiRegistre no Claude Code
claude mcp add rd-station-crm -s user -- node "$(pwd)/dist/index.js"Confirme com:
claude mcp listDeve aparecer
rd-station-crm ... ✔ Connected.Registre no Codex CLI
codex mcp add rd-station-crm -- node "$(pwd)/dist/index.js"Se o comando
codexnão existir no seu PATH, use o caminho do binário do app do ChatGPT/Codex (no Linux costuma ser/usr/lib/chatgpt/resources/codex) no lugar decodexno comando acima.Confirme com:
codex mcp listTeste Abra uma sessão nova do Claude Code ou do Codex (
claude/codexno terminal) e peça algo como:lista meus contatos do RD Station
Se ele chamar a tool
rdstation_list_contactse trazer dados reais, está tudo certo.
Importante sobre o app do ChatGPT (web/desktop)
Esse servidor roda local, via stdio, então funciona com Claude Code e Codex CLI. O app do ChatGPT (Settings → Apps & Connectors → Developer mode) só aceita servidores MCP remotos, via HTTPS — não é possível apontar para um script local. Para usar lá seria necessário hospedar este servidor publicamente e trocar o transporte para HTTP, o que este projeto não faz hoje.
Ferramentas disponíveis
Contatos: rdstation_list_contacts, rdstation_get_contact, rdstation_create_contact,
rdstation_update_contact, rdstation_delete_contact
Organizações: rdstation_list_organizations, rdstation_get_organization
Negócios: rdstation_list_deals, rdstation_get_deal, rdstation_create_deal,
rdstation_update_deal, rdstation_win_deal, rdstation_lose_deal
Pipelines: rdstation_list_deal_pipelines, rdstation_list_deal_stages
Usuários: rdstation_list_users
Desenvolvimento
Depois de alterar algo em src/, é preciso buildar de novo para o Claude/Codex
pegarem a mudança (eles executam dist/index.js, não o .ts):
npm run buildAvailable Tools
16 toolsrdstation_create_contactA
Create a contact in RD Station CRM. contact is the raw request body per the RD Station CRM API (e.g. { name, emails: [{ email }], phones: [{ phone, type }], organization_id, title }).
Inputs: contact (required).
rdstation_create_dealB
Create a deal in RD Station CRM. deal is the raw request body per the RD Station CRM API (e.g. { name, deal_pipeline_id, deal_stage_id, contact_ids: [...], organization_id }).
Inputs: deal (required).
rdstation_delete_contactB
Delete a contact from RD Station CRM by id.
Inputs: contact_id (required).
rdstation_get_contactA
Get a single contact from RD Station CRM by id.
Inputs: contact_id (required).
rdstation_get_dealB
Get a single deal from RD Station CRM by id.
Inputs: deal_id (required).
rdstation_get_organizationA
Get a single organization from RD Station CRM by id.
Inputs: organization_id (required).
rdstation_list_contactsC
List contacts from RD Station CRM.
Inputs: page, limit.
rdstation_list_deal_pipelinesA
List deal pipelines (funis) configured in RD Station CRM.
Inputs: no named parameters.
rdstation_list_dealsB
List deals (negócios) from RD Station CRM.
Inputs: page, limit.
rdstation_list_deal_stagesA
List the stages of a deal pipeline in RD Station CRM. Omit deal_pipeline_id to list all pipelines with their stages.
Inputs: deal_pipeline_id.
rdstation_list_organizationsB
List organizations (companies) from RD Station CRM.
Inputs: page, limit.
rdstation_list_usersA
List users (team members) from RD Station CRM.
Inputs: page, limit.
rdstation_lose_dealC
Mark a deal as lost in RD Station CRM, optionally with a lost reason id and note.
Inputs: deal_id (required), note, deal_lost_reason_id.
rdstation_update_contactC
Update fields of an existing contact in RD Station CRM.
Inputs: contact (required), contact_id (required).
rdstation_update_dealC
Update fields of an existing deal in RD Station CRM.
Inputs: deal (required), deal_id (required).
rdstation_win_dealB
Mark a deal as won in RD Station CRM.
Inputs: deal_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct resource-action pair: contact CRUD, organization read, deal management, pipeline/stage listing, and user listing. Actions like win_deal and lose_deal are clearly separate from generic update_deal, so there is no real ambiguity.
All tools share the rdstation_ prefix and follow a consistent snake_case verb_noun pattern (list_contacts, get_contact, update_deal, win_deal). The naming is predictable and makes the tool family easy to navigate.
At 16 tools, the set is at the upper edge of the ideal range but each tool maps to a meaningful CRM operation. The breakdown across contacts, deals, organizations, pipelines, and users is reasonable, though it is slightly heavy.
Contacts have full CRUD coverage and deals cover the main lifecycle including win/lose, but organizations are read-only with no create/update/delete. There is also no deal deletion, which leaves notable lifecycle gaps for the stated CRM domain.
Maintenance
Related MCP Connectors
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Native MCP access to CRM contacts, organizations, deals and tasks with user permissions.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server that exposes the Poli Júnior Pipedrive CRM to Claude as composable tools.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with full access to HubSpot CRM. Manage contacts, companies, deals, pipelines, and associations directly from Claude, Cursor, or any MCP-compatible client.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for RD Station Marketing enabling AI agents to manage contacts, conversion events, webhooks, and account info via OAuth 2.0.MIT
- AlicenseAqualityDmaintenanceAn MCP server for RD Station CRM that enables managing contacts, deals, tasks and notes, and generating pipeline health reports through natural language in any MCP-compatible client like Claude.1255 npmMIT