Skip to main content
Glama
bratland

Pipedrive MCP Server

by bratland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pipedrive MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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 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

    • 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/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource type (activities, deals, organizations, persons, etc.) and action (get vs. search). However, some ambiguity exists between 'get_overview', 'get_quarter_summary', and 'get_quarterly_progress', which all provide high-level metrics and could be confused for overlapping purposes. The search tools also have some overlap (e.g., 'search_items' vs. specific resource searches), but descriptions help differentiate them.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. All tools start with 'get_' or 'search_', followed by the resource name (e.g., 'get_deals', 'search_persons'), with variations like 'summary' or specific qualifiers (e.g., 'get_current_quarter_deals') maintaining this structure. There are no deviations in naming conventions.

    Tool Count3/5

    With 30 tools, the count is borderline high for a CRM server, as it includes many specialized variants (e.g., summary versions, quarterly tools) that might be excessive. While Pipedrive's domain is broad, 30 tools feels heavy and could overwhelm agents, though not extreme. A more streamlined set of 15-20 tools might be more appropriate.

    Completeness4/5

    The tool surface provides comprehensive read/search coverage for core CRM resources (deals, persons, organizations, activities, notes, users, pipelines, stages) with both detailed and summary views. However, there are notable gaps in write operations (e.g., create, update, delete), which are essential for full lifecycle management in a CRM system. Agents can perform queries effectively but may fail when needing to modify data.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources