Kommo MCP Server
Related Servers
Alternatives to Kommo MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage Kommo CRM (formerly AmoCRM) entities including leads, contacts, companies, tasks, notes, pipelines, and products through natural language commands via the Model Context Protocol.399 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.15 npmMIT
- AlicenseBqualityCmaintenanceSelf-hosted MCP server that connects AI assistants to Kommo CRM (API v4), enabling real-time CRM actions such as creating/managing leads, tasks, notes, and more through 29 tools.291MIT
- AlicenseBqualityAmaintenanceEnables comprehensive integration with Kommo CRM through 25 tools for managing leads, contacts, companies, tasks, events, and generating detailed analytics reports. Supports advanced workflow management, pipeline operations, and real-time performance tracking.2214MIT
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to the Ploomes CRM, exposing 153 tools for CRUD operations on entities, pipeline and field configuration, CPQ proposal models, automations, and webhooks.-
- FlicenseCqualityCmaintenanceExposes 153 tools to connect AI assistants to the Ploomes CRM, enabling CRUD operations, funnel configuration, CPQ, automations, and webhooks.1001-
TDQS
Scored across 27 tools
Each tool targets a distinct resource or action (e.g., leads, contacts, pipelines, custom fields, tasks, webhooks, WhatsApp, salesbot). Overlapping purposes like search_leads vs get_lead are clearly differentiated by intent (search vs retrieve by ID). No two tools are ambiguous.
Tool names consistently follow a verb_noun pattern in snake_case (e.g., create_lead_complex, get_pipelines, send_whatsapp_message). Minor inconsistencies exist, such as 'manage_lead_tags' instead of 'add_remove_lead_tags' and 'add_lead_note' vs 'create_task', but the pattern is generally clear and predictable.
27 tools is on the higher side for an MCP server, but the comprehensive coverage of a CRM API including leads, contacts, companies, pipelines, custom fields, tasks, webhooks, and special actions (WhatsApp, salesbot, raw API) justifies the count. Slight over-scoping, but each tool serves a distinct purpose.
The server lacks delete operations for all major entities (leads, contacts, companies, pipelines, tasks, etc.), which is a notable gap in lifecycle coverage. Additionally, there is no list_all_leads or list_all_tasks tool; search tools may compensate but are not equivalent. The raw API request can fill some gaps, but the surface is incomplete for full CRUD.