1c-odata-mcp vs ERPNext by Cotlet
1c-odata-mcp is an MCP server published by evilbruce666. Marketplaces we read that list it: 1 (npm registry (MCP servers)). ERPNext by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  1c-odata-mcp |  ERPNext by Cotlet |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.14.0 Downloads/month (npm): 1 754 Downloads/week (npm): 884 Forks (GitHub): 15 Stars (GitHub): 43 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | 1c-odata-mcp | ERPNext by Cotlet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 43 | No figure on GitHub |
| Forks (GitHub) (differs) | 15 | No figure on GitHub |
| Last release (differs) | 2026-11-07 | Not published |
| Where it runs (differs) | On your machine (1c-odata-mcp) | Remote server (cotlet.dev/mcp/v1/erpnext/connect) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/evilbruce666/1c-odata-mcp | Not stated |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-12 | 2026-11-09 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
1c-odata-mcp
MCP server for 1C:Enterprise (1С) over OData. Ask your accounting database in natural language — debtors and creditors by due date, unpaid invoices, cash on hand, month-close checks, account cards, reconciliation statements, sales, taxes, cash flow, accou
ERPNext by Cotlet
Invoices, payments, customers and stock in ERPNext.
How to run each
1c-odata-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ERPNext by Cotlet As a remote MCP server
claude mcp add --transport http erpnext https://cotlet.dev/mcp/v1/erpnext/connectCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: 1c-odata-mcp · What it can do: ERPNext by Cotlet · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.