Skip to main content
Glama
WillDent

Pipedrive MCP Server

by WillDent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Pipedrive MCP Server

No user-submitted related servers found.

    Related Servers

    • Pipedrive MCP Server

      bratland
      A
      license
      B
      quality
      C
      maintenance
      Connects the Pipedrive API v2 to LLM applications, providing read-only access to CRM data including deals, contacts, and pipelines. It enables users to search and retrieve organization information, activities, and notes through natural language.
      30
      1,053 npm
      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
      259 npm
      8
      MIT

    • Pipedrive MCP Server

      agranig
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to analyze Pipedrive sales pipeline, deal velocity, and activity engagement, helping sales teams understand where deals are stalling.
      7
      1,053 npm
      MIT
    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 16 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation (e.g., get-deals vs. get-deal vs. search-deals). The differences are clear from descriptions, reducing ambiguity.

    Naming Consistency5/5

    All tools use a consistent verb_noun pattern (e.g., get-users, search-persons). List operations use plural nouns, single retrieval uses singular, and searches are prefixed with 'search-'.

    Tool Count4/5

    With 16 tools, the count is slightly above the typical 3-15 range but still reasonable for covering multiple CRM entities. No tools are redundant.

    Completeness2/5

    Only read operations are provided (list, get, search). Missing create, update, delete tools, which are essential for a CRM server. Agents cannot perform any write actions.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources