Skip to main content
Glama
ppiotis

Solo CRM MCP

Official
by ppiotis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Solo CRM MCP

No user-submitted related servers found.

    Related Servers

    • agent-crm

      clayton
      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

    • FolderBridge MCP

      MoonTzai
      A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to inspect and carefully edit a bounded local workspace via stdio, with a read-only default, conflict-safe updates, and no network listener or telemetry.
      10
      2
      Apache 2.0

    • Personal Filebridge

      egormakarenkov
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled local Windows file inspection, reading, writing, reversible deletion, restoration, and auditing across user-selected folder roots. Commits occur only after separate owner approval in a native desktop dialog, while the tool cannot bypass OS security controls.
      MIT

    • notes-box

      Ioniq3423
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Desktop to manage personal notes stored in a JSON file, supporting add, get, update, delete, and list operations with atomic saves.
      MIT

    • Demo CRM MCP Server

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

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: contacts (list/get/upsert/delete), deals (list/upsert/delete), follow-ups (list/add/complete), activities (log), analytics (pipeline_summary), and outreach drafting. No two tools overlap in function, and the two-step confirmation applies uniformly to all mutating tools, so there is no ambiguity about which tool to use for a given operation.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun or noun_verb pattern (list_contacts, get_contact, upsert_deal, add_follow_up, complete_follow_up, pipeline_summary). Verbs are standard CRM terms and suffixes are predictable, making the naming pattern easy to learn.

    Tool Count5/5

    13 tools is well-scoped for a CRM: read operations (list/get/pipeline_summary), full create/update/delete for contacts and deals, and follow-up lifecycle management. No redundant or trivial tools; each earns its place.

    Completeness5/5

    The surface covers the core CRM lifecycle: contact CRUD, deal CRUD, follow-up scheduling/completion, activity logging, pipeline analytics, and outreach drafting. There are no obvious gaps for the stated domain; the only limitation (no message sending) is explicitly noted and is not a CRUD gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources