rd-station-crm
Related Servers
Alternatives to rd-station-crm
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn 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.1231 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
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server that exposes the Poli Júnior Pipedrive CRM to Claude as composable tools.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to access amoCRM data such as pipelines, deals, contacts, and users via the MCP protocol.6 npmMIT
- 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.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.28 npm2MIT
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.