Kommo Kiro MCP
Related Servers
Alternatives to Kommo Kiro MCP
- FlicenseBqualityDmaintenanceEnables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.271-
- 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.3912 npm1MIT
- AlicenseAqualityFmaintenanceEnables managing amoCRM data through natural language, including leads, contacts, companies, pipelines, tasks, notes, search, events, and unsorted leads.1968 npmMIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables integration with Kommo CRM to manage leads, add notes and tasks, update custom fields, and list pipelines. Supports multi-tenant authentication and includes an approval system for bulk operations.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.12 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-
- 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
- FlicenseBqualityDmaintenanceEnables AI assistants to manage CRM deals and tasks on Aspro Cloud, including CRUD operations on deals, tasks, users, pipelines, and workflows.16-
- AlicenseBqualityDmaintenanceSelf-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
TDQS
Scored across 30 tools
Each tool targets a distinct resource+action, and the descriptions explicitly steer callers between the overlapping pairs (update_lead vs move_lead_stage vs bulk_update_leads, create_lead vs create_lead_complex, add_note vs send_chat_message). A few tools legitimately overlap (bulk vs single update, complex vs simple create) but the descriptions disambiguate them well.
Nearly all names follow a clean snake_case verb_noun pattern (list_leads, get_contact, create_pipeline, update_stage, delete_lead). Minor variants like move_lead_stage, create_lead_complex, and bulk_update_leads still fit the verb+noun shape and stay readable.
30 tools is on the heavy side, but the surface spans many distinct entities (leads, contacts, companies, pipelines, stages, custom fields, tags, tasks, notes, chat), so the count is justified. Each tool earns its place rather than being redundant, though it sits just above the comfortable band.
Leads have full CRUD plus stage/tag/notes, but several entities are partial: no delete_contact, no delete_company/get_company/update_company, no update/delete for custom fields, and tasks can be created and listed but not updated or completed. These gaps will force workarounds for common lifecycle operations.