Skip to main content
Glama
meshachjackson

mcp-nimble-crm

Related Servers

Alternatives to mcp-nimble-crm

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Nimble CRM API, enabling management of contacts, deals, notes, tasks, and tags through natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.
      5 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Keap CRM, providing tools to manage contacts, tags, opportunities, notes, tasks, campaigns, and users via the Keap REST API v1.
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables reading and managing Pipedrive CRM records—deals, people, organizations, activities, and notes—over MCP, including searching, writing, and moving deals through pipelines.
      Apache 2.0
    • 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.
      28 npm
      2
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides an interface to the Copper CRM API for managing contacts, companies, activities, and opportunities. It enables users to search for people, log meetings or notes, and track sales deals directly through MCP-compatible clients.
      9
      -

    TDQS

    B3.2/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs, but a few like create_note/create_contact_note and get_contacts_by_ids/get_contact could cause misselection. Descriptions generally clarify the differences, though the sheer number of tools increases the chance of confusion.

    Naming Consistency5/5

    All tool names consistently use snake_case with a verb_noun or verb_noun_qualifier pattern. Even exceptions like exit_lead_successful and get_won_deals_last_month follow the verb-first convention.

    Tool Count2/5

    At 62 tools, the server is far beyond the typical well-scoped range. While the broad CRM domain partly justifies the count, the sheer number creates unwieldy navigation and includes redundant variants like delete_contact, delete_contacts, and delete_contacts_by_query.

    Completeness3/5

    Contact, deal, pipeline, and note coverage is robust, but tasks and activities only support create/list with no update/delete, and message drafts lack update/delete/send. These are notable lifecycle gaps for a CRM.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues