Pipedrive MCP Server
Related Servers
Alternatives to Pipedrive MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables LLMs like Claude to interact with Pipedrive CRM data through a standardized interface, providing 22 tools for managing deals, persons, organizations, activities, and more.221MIT
- AlicenseBqualityFmaintenanceEnables natural language interaction with Pipedrive CRM via Claude Code, allowing users to manage deals, contacts, activities, and more through conversational commands.2611 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides full CRUD access to Pipedrive CRM API, enabling Claude and other LLM applications to manage deals, persons, organizations, activities, notes, and leads with advanced filtering and fuzzy search capabilities.100 npm6MIT
- AlicenseBqualityAmaintenanceEnables users to manage Pipedrive CRM data including deals, contacts, and activities directly through an AI assistant. It supports full CRUD operations, email engagement analysis, and mapping of custom field metadata for comprehensive pipeline management.123312 npm10MIT
- AlicenseBqualityCmaintenanceEnables read-only access to Pipedrive data including deals, persons, organizations, and pipelines, allowing LLMs like Claude to query and analyze CRM information through natural language.16100 npm60MIT
- FlicenseBqualityDmaintenanceEnables to manage Pipedrive deals, activities, persons, organizations, and custom fields with automatic backup and restore capabilities, allowing safe pipeline management via natural language.28-
TDQS
Scored across 303 tools
With 303 tools there are numerous near-duplicates: system_get_current_user vs users_get_current vs users_get, search_deals vs deals_search vs search_universal, and three listing variants (persons_list, persons_list_all_auto, persons_get_collection). These overlapping tools make selection ambiguous for an agent even with detailed descriptions.
Most tools follow an entity_action pattern (deals_get, persons_update, teams_create), but several break it with verb-first names (search_universal, search_deals, search_persons, search_by_field) and singular/plural inconsistencies (users_find vs persons_search, lead_labels_create vs leads_get_labels). Still readable but not a single predictable convention.
303 tools is an extreme mismatch for practical agent use; the surface is far beyond well-scoped, with many redundant list/search/current-user variants that could be consolidated. This makes discovery and correct tool selection very difficult.
Coverage is extremely broad—CRUD, bulk operations, followers, fields, pipelines, webhooks, lead/deal conversion, etc.—with few true gaps. Minor dead ends exist (e.g., channels can be created/deleted but not updated, no user delete), but core CRM lifecycles are comprehensively covered.