Kommo CRM vs Butterbase Oss
A side-by-side look at the Kommo CRM and Butterbase Oss MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
Kommo CRMKnowledge & Memory · Local subprocess (stdio)Manage Kommo CRM leads, contacts, pipelines, tasks, notes, tags and companies.40FairAuth: not declaredVerdict: choose Kommo CRM for knowledge & memory work as a local process; choose Butterbase Oss for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
KChoose Kommo CRM when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KOMMO_SUBDOMAIN, KOMMO_ACCESS_TOKEN.
Choose Butterbase Oss when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Kommo CRM | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | KOMMO_SUBDOMAINKOMMO_ACCESS_TOKEN | None listed |
| Verified owner |
Tools & capabilities
Kommo CRM tools
No tool names declared yet. Check the project README from the listing page.
Butterbase Oss tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kommo CRM
{
"mcpServers": {
"kommo-crm": {
"command": "uvx",
"args": [
"--from",
"kommo-kiro-power",
"kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "YOUR_KOMMO_SUBDOMAIN_HERE",
"KOMMO_ACCESS_TOKEN": "YOUR_KOMMO_ACCESS_TOKEN_HERE"
}
}
}
}
Butterbase Oss
{
"mcpServers": {
"mcp-285": {
"command": "npx",
"args": [
"-y",
"@butterbase/mcp"
]
}
}
}
Frequently asked questions
Kommo CRM is categorized under Knowledge & Memory and uses a local stdio subprocess. Butterbase Oss belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Kommo CRM for knowledge & memory work and Butterbase Oss for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kommo CRM has no declared pricing — check the project's own site. Butterbase Oss has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kommo-crm and mcp-285 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kommo CRM has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Butterbase Oss has 51/100 (Good) with 1 views, 0 installs and 3,687 GitHub stars.