Skip to main content
Glama
alvarolloret

Miinta Pipedrive MCP

by alvarolloret
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Miinta Pipedrive MCP

No user-submitted related servers found.

    Related Servers

    • crm-mcp-server

      rahulvai05
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server providing structured access to CRM data (companies, contacts, deals, activities) backed by SQLite. It enables LLMs to search contacts and deals, view full company accounts, find stale deals, and get pipeline summaries.
      -

    • pipedriver

      vaibhavpandeyvpz
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      93 npm
      2
      MIT

    • pipedrive-pj

      hguareromanoo
      F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that exposes the Poli Júnior Pipedrive CRM to Claude as composable tools.
      -

    • was-pipedrive-mcp

      mnsmasum62786
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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

    • Uniware Vtiger MCP Server

      Srimathi-8502
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server connecting Claude to Vtiger CRM for leads, deals, and overdue follow-ups.
      -
    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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: list, create, delete filters, and get the sales queue. The sales queue tool depends on filters but does not overlap with filter CRUD operations. No ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent `miinta.<resource>.<action>` pattern: `miinta.filters.list`, `miinta.filters.delete`, `miinta.filters.create`, and `miinta.sales_queue.get`. The convention is uniform and predictable.

    Tool Count5/5

    With four tools, the set is concise and well-scoped for managing filters and retrieving a sales queue. It fits within the ideal 3-15 range and each tool is necessary for the intended workflow.

    Completeness4/5

    Filter CRUD is partially covered: create, list, delete, but no update or get-by-id. The sales queue tool is the core feature and works via filters. Minor gaps exist but can be worked around by deleting/recreating filters.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources