pipedrive-mcp
Related Servers
Alternatives to pipedrive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA self-contained MCP server for Pipedrive CRM that exposes 27 tools allowing AI coding assistants to read, create, update, search, and manage deals, contacts, activities, organizations, leads, and pipelines.MIT
- AlicenseNot gradedqualityDmaintenanceUniversal MCP server for Pipedrive, enabling interaction with Pipedrive's tools and services through a standardized API.1MIT
- AlicenseNot gradedqualityDmaintenanceComprehensive MCP server for Pipedrive CRM with 118 tools and 27 UI apps, enabling full CRM operations via natural language.40 npmMIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server for the Pipedrive CRM API, enabling AI assistants to read, write, and analyze CRM data conversationally through 100 tools including performance reporting and loss analysis.54 npm8MIT
- 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.11 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables reading and managing Pipedrive CRM records—deals, people, organizations, activities, and notes—over MCP, including searching, writing, and moving deals through pipelines.Apache 2.0
TDQS
Scored across 93 tools
While most tools target distinct resources and actions, the set includes several overlapping convenience wrappers (e.g., pipedrive_deals_summary vs pipedrive_my_pipeline_summary, pipedrive_my_open_deals vs pipedrive_deals_list, and the similarly named pipedrive_product_deals_list vs pipedrive_deal_products_list). Descriptions help clarify intent, but an agent still faces multiple ambiguous pairs.
All tools use the pipedrive_ prefix and snake_case with a generally consistent entity_action pattern. Minor deviations exist (e.g., reversed entity order in pipedrive_product_deals_list vs pipedrive_deal_products_list; singular pipedrive_mail_thread_messages_list vs plural pipedrive_mail_threads_list), but naming is largely predictable.
93 tools is an extreme mismatch for a single MCP server; even for a broad CRM like Pipedrive, this far exceeds the well-scoped 3-15 range. Many tools are convenience wrappers that could be consolidated or parameterized to reduce surface area.
Core CRM entities (deals, persons, orgs, leads, activities, notes, products, mail) have near-complete CRUD/search coverage with useful lifecycle operations like merge, move_stage, and mark_done. Gaps remain for filter create/update/delete, webhook update, and pipeline/stage management, but these are relatively minor for agent workflows.