Solo CRM MCP
OfficialRelated Servers
Alternatives to Solo CRM MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceEnables Claude to record job applications in a local JSON file and then list them, change their status (applied, replied, interview, rejected, offer), and surface stale applications that need a follow-up. Requires no database or account, and validates every input so saves stay clean.41MIT
- AlicenseNot gradedqualityCmaintenanceEnables tracking of job applications and freelance leads through an MCP interface, with tools to add and update items, list and summarize the pipeline, flag stale entries, and draft follow-up messages grounded in each item's logged notes using locally stored JSON data.MIT
- AlicenseAqualityAmaintenanceEnables users to track job and internship applications, statuses, deadlines, and interviews, with upcoming reminders and CSV or Markdown export. It runs locally and stores data in a single JSON file without network calls, accounts, or API keys.8561 npmMIT
- AlicenseAqualityAmaintenanceEnables 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.102Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
TDQS
Scored across 13 tools
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.
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.
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.
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.