capsulemcp
Related Servers
Alternatives to capsulemcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLoomio tools for Claude. Local install via npx, org-wide via Custom Connectors. Read-only mode supported.2484 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read local CRM records, capture notes, and propose updates through MCP while keeping human approval in the dashboard or CLI. It supports querying relationships, follow-ups, tickets, and qualification data backed by SQLite.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to search a CRM account's contacts and deals, add notes, and create follow-up tasks, exposing read-only and additive-write tools over a bearer-token-protected Streamable HTTP endpoint. No tool can delete or edit existing records.MIT
- FlicenseBqualityDmaintenanceConnects Claude to your JobNimbus account via API, enabling management of contacts, jobs, notes, and other CRM entities through natural language.19-
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing a CRM database through natural language conversations with Claude Desktop.-

Evo CRM MCPofficial
AlicenseBqualityCmaintenanceEnables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.12MIT
TDQS
Scored across 92 tools
Most tools have clearly distinct purposes, and the descriptions actively route callers between search, filter, list, single-get, and batch-get variants. However, with 92 tools there is residual ambiguity across overlapping surfaces such as search_parties/filter_parties, list_projects/search_projects/filter_projects, and list_entries/list_activities/list_*_entries.
Tool names follow a consistent snake_case verb_noun pattern: get_*, list_*, create_*, update_*, delete_*, add_*, remove_*, search_*, filter_*, batch_*, and run_*. Variants such as remove_*_by_id and batch_update_* are meaningful and predictable rather than inconsistent.
92 tools is far beyond an appropriate surface for a single MCP server, even for a broad CRM. The set includes many granular CRUD, batch, reference, audit, and diagnostic tools, creating high selection and maintenance overhead for an agent.
The server covers core CRM lifecycle operations extremely well: parties, opportunities, projects, tasks, entries, tags, tracks, attachments, reference data, audit lists, and batch operations are all represented. Minor gaps remain around configuration objects such as pipelines, milestones, boards, stages, custom fields, and track definitions, plus attachment update/delete and some batch create/delete workflows.