Skip to main content
Glama
jonnyanarx

Freshsales MCP Server

by jonnyanarx

Related Servers

Alternatives to Freshsales MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools to interact with GoHighLevel CRM data, including contacts, conversations, call transcripts, broker lead overviews, pipelines/opportunities, and task creation. Supports both stdio and HTTP transports for local and remote use.
      -
    • F
      license
      B
      quality
      B
      maintenance
      Enables managing a small CRM of companies, contacts, deals, and activities through MCP tools, including creating and updating records, logging activities, searching across the CRM, and summarizing pipeline stages.
      15
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP-native CRM backend for AI agents, enabling customer, opportunity, note, follow-up, and pipeline health management through 15 MCP tools.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes CRM operations as MCP tools, enabling agents to search contacts, retrieve contact records, list appointments, log notes, and create new leads.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Full-featured Pipedrive MCP server for Claude Desktop, enabling natural language control over deals, leads, persons, organizations, notes, activities, pipelines, and more via 34 tools and 7 prompts.
      9 npm
      MIT

    TDQS

    C2.7/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes based on entity and action (e.g., create_lead, update_deal, search_contacts). However, the unified 'search' tool overlaps with the entity-specific search tools (search_leads, search_contacts, etc.), which could cause some confusion about which to use.

    Naming Consistency4/5

    Tools predominantly follow a consistent verb_noun pattern (e.g., list_leads, create_contact, update_account). The only notable deviation is the standalone 'search' tool, which lacks a noun component, but otherwise the naming is predictable.

    Tool Count2/5

    With 30 tools, the server is on the heavy side for its scope. While the tools are organized by entity, the sheer number (exceeding 25) may overwhelm an agent and increase selection complexity.

    Completeness3/5

    Core CRUD operations are covered for leads, contacts, accounts, and deals (create, read, update, list, search), but delete operations are entirely missing for all entities. This is a notable gap in the lifecycle, though agents can still manage most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues