kommo-mcp
Related Servers
Alternatives to kommo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server that exposes the Kommo CRM API v4 (plus Files, Conversations, and analytics helpers) as Model Context Protocol tools, resources, and prompts.100MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.6427 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for amoCRM integration, enabling AI assistants to manage leads, contacts, companies, tasks, and more via natural language.4MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that lets AI validate and create sales funnels (pipelines, stages, custom fields) in Kommo CRM, supporting multiple client accounts with explicit confirmation before writing.-
- AlicenseNot gradedqualityBmaintenanceMCP server that auto-discovers Kama CRM API endpoints from OpenAPI spec and exposes them as tools for AI agents to perform CRM operations via natural language.38 npmMIT
- FlicenseNot gradedqualityDmaintenanceAI-powered CRM assistant for Kommo/amoCRM that provides natural language management via Telegram bot and MCP protocol, enabling analytics, entity operations, and CRM setup.8-
TDQS
Scored across 29 tools
Each tool has a clear and distinct purpose, targeting specific entities (leads, contacts, companies, tasks, webhooks, custom fields, pipelines, statuses, users, events) and actions (create, update, get, search, list, delete/subscribe). There is no ambiguity between tools; even similar verbs (e.g., create vs update) are well separated by entity.
The naming convention is predominantly 'kommo_verb_noun' in English (e.g., create_lead, search_companies, list_tasks). However, two tools break the pattern: 'kommo_link' (should be something like link_entity) and 'kommo_pipelines' (should be list_pipelines). These minor inconsistencies slightly reduce consistency.
29 tools is on the higher side but appropriate for a comprehensive CRM integration covering leads, contacts, companies, tasks, webhooks, custom fields, pipelines, statuses, users, and events. The count reflects necessary CRUD operations plus search and administrative tools. No obvious bloat.
The tool set covers most expected CRM operations: CRUD for leads, contacts, companies, custom fields, statuses; task management; webhook subscription; user listing; and event tracking. Notable gaps include missing delete operations for leads, contacts, companies, and tasks, but these can be addressed via the generic API passthrough ('kommo_request'). Overall, the surface is nearly complete.