Skip to main content
Glama
nubiia-dev

Pipedrive MCP Server

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pipedrive MCP Server

No user-submitted related servers found.

    Related Servers

    • Pipedrive MCP Server

      osherai
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs like Claude to interact with Pipedrive CRM data through a standardized interface, providing 22 tools for managing deals, persons, organizations, activities, and more.
      22
      1
      MIT

    • Pipedrive MCP

      expertintegrado
      A
      license
      B
      quality
      F
      maintenance
      Enables natural language interaction with Pipedrive CRM via Claude Code, allowing users to manage deals, contacts, activities, and more through conversational commands.
      26
      11 npm
      MIT

    • Pipedrive MCP Server

      ckalima
      A
      license
      B
      quality
      A
      maintenance
      Enables 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.
      123
      118 npm
      8
      MIT

    • Pipedrive MCP Server

      WillDent
      A
      license
      B
      quality
      A
      maintenance
      Enables 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.
      16
      1,053 npm
      60
      MIT

    • mcp-pipedrive

      leonardoceron-yvy
      F
      license
      B
      quality
      D
      maintenance
      Enables to manage Pipedrive deals, activities, persons, organizations, and custom fields with automatic backup and restore capabilities, allowing safe pipeline management via natural language.
      28
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 303 tools

    Disambiguation4/5

    Most tools are clearly scoped by resource (deals, persons, organizations, products, leads) and action (list, create, update, delete). However, there are several pairs that could be confused: deals_list_field_updates vs deals_list_updates vs deals_list_participant_updates all provide different update feeds; users_get_current vs system_get_current_user both return the current user; leads_convert_to_deal and deals_convert_to_lead are distinct but could be mistaken for each other.

    Naming Consistency4/5

    The tool names follow a consistent <entity>_<action> pattern (e.g., deals_list, deals_create, deals_update). A few minor deviations exist such as 'systems_get_current_user' instead of 'users_get_current' and 'lead_labels_create' vs 'leads_get_labels', but overall the pattern is clear and predictable.

    Tool Count2/5

    With 303 tools, this server is vastly over-scoped for a typical agent. The sheer number makes it difficult for an agent to discover and select the right tool, even though each individual tool may be well-defined. A more curated set of essential CRUD and workflows would be more appropriate.

    Completeness4/5

    The server covers the full lifecycle for core entities (deals, persons, organizations, products, leads, activities, notes, files) including create, read, update, delete, search, add/remove followers, and basic analytics. However, there are gaps in edge-case operations like webhook management, permissions, and custom fields, though they are present, and the completeness of specific workflows like lead conversion is supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources