NOVA MCP connector for Kommo vs Attio MCP Server
NOVA MCP connector for Kommo is an MCP server published by nova-kommo.com. Marketplaces we read that list it: 1 (Official MCP Registry). Attio MCP Server is an MCP server published by kesslerio. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Attio MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.7.0 Downloads/month (npm): 2 390 Downloads/week (npm): 633 Forks (GitHub): 23 Stars (GitHub): 68 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.7.0 Downloads/month (npm): 2 390 Downloads/week (npm): 633 Forks (GitHub): 23 Stars (GitHub): 68 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | NOVA MCP connector for Kommo | Attio MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 68 |
| Forks (GitHub) (differs) | No figure on GitHub | 23 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (sp1-nova.com/api/mcp-server/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | Not stated | github.com/kesslerio/attio-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 9 h ago | Status out of date: last check 35 h ago returned HTTP 404 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
NOVA MCP connector for Kommo
Remote MCP for Kommo CRM: leads, contacts, tasks, notes, pipelines, chats, Salesbot. OAuth.
Attio MCP Server
AI-powered Attio CRM access. Manage contacts, companies, deals, tasks, notes and workflows.
How to run each
NOVA MCP connector for Kommo As a remote MCP server
claude mcp add --transport http kommo https://sp1-nova.com/api/mcp-server/mcp/Attio MCP Server As a local MCP server: npm package
claude mcp add --env "ATTIO_API_KEY=<YOUR_ATTIO_API_KEY>" --transport stdio attio-mcp-server -- npx -y attio-mcpRequires: ATTIO_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of NOVA MCP connector for Kommo responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of NOVA MCP connector for Kommo publish no settings it asks for, so we do not compare settings.
What it can do: NOVA MCP connector for Kommo · What it can do: Attio MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.