capsulemcp
Related Servers
Alternatives to capsulemcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLoomio tools for Claude. Local install via npx, org-wide via Custom Connectors. Read-only mode supported.1211 npmApache 2.0
- FlicenseBqualityBmaintenanceConnects 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.-
- AlicenseBqualityFmaintenanceEnables natural language interaction with Pipedrive CRM via Claude Code, allowing users to manage deals, contacts, activities, and more through conversational commands.2611 npmMIT

@lcapps/mcp-crmofficial
AlicenseNot gradedqualityCmaintenanceConnects your LCApps CRM with AI assistants like Claude, enabling querying and creation of CRM data such as clients, invoices, and expenses. Optionally allows saving PDF documents locally when used as a package.MIT- FlicenseNot gradedqualityDmaintenanceIntegrates Zero CRM with Claude Desktop, providing 16 tools for full CRUD operations on companies, contacts, and deals with filtering and pagination.-
TDQS
Scored across 92 tools
Each tool targets a clear, distinct action on a specific entity (party, opportunity, project, task, etc.), with no obvious overlap. Even closely related tools like search_parties vs filter_parties are clearly differentiated by their descriptions, and batch variants are explicitly marked for multi-item operations.
Tool names consistently follow a verb_noun pattern (e.g., create_party, get_party, update_party, delete_party). Batch operations are uniformly prefixed with 'batch_', and entity-specific list operations follow a consistent 'list_<entity>_<subresource>' structure. Minor deviations like 'add_party_address' vs 'remove_party_address_by_id' are still systematic.
With 92 tools, the server is far beyond the typical well-scoped range. While the domain is broad (parties, opportunities, projects, tasks, entries, tracks, reference data), the number is excessive. Many tools are batch variants and atomic child-entity operations that could be consolidated, making the tool surface overwhelming for an agent to navigate.
The tool set covers the full lifecycle for all core entities: create, read, update, delete, batch operations, search/filter, tags, tracks, entries, and reference data. It even includes audit features (deleted entities) and diagnostics (get_current_user). There are no obvious missing operations for a Capsule CRM integration; the surface is comprehensive.