SnelStart MCP Server and API by Cotlet vs io.github.lazyants/lexware
SnelStart MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.lazyants/lexware is an MCP server published by lazyants. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  SnelStart MCP Server and API by Cotlet |  io.github.lazyants/lexware |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 5.4.1 Downloads/month (npm): 2 536 Downloads/week (npm): 650 Forks (GitHub): 6 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 5.4.1 Downloads/month (npm): 2 536 Downloads/week (npm): 650 Forks (GitHub): 6 Stars (GitHub): 8 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 | SnelStart MCP Server and API by Cotlet | io.github.lazyants/lexware |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 8 |
| Forks (GitHub) (differs) | No figure on GitHub | 6 |
| Last release (differs) | 2026-11-09 (better) | 2026-11-07 (worse) |
| Where it runs (differs) | Remote server (cotlet.dev/mcp/v1/snelstart/connect) | On your machine (@lazyants/lexware-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Not stated | FSL-1.1-MIT |
| Repository (differs) | Not stated | github.com/lazyants/lexware-mcp-server |
| Changes in the last 7 days (differs) | 5 | 2 |
| First seen (differs) | 2026-11-09 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
SnelStart MCP Server and API by Cotlet
SnelStart MCP server: create sales invoice, add relation, book entry, list open items.
io.github.lazyants/lexware
MCP server for the Lexware Office API — invoices, contacts, articles, and vouchers.
How to run each
SnelStart MCP Server and API by Cotlet As a remote MCP server
claude mcp add --transport http snelstart https://cotlet.dev/mcp/v1/snelstart/connectio.github.lazyants/lexware As a local MCP server: npm package
claude mcp add --env "LEXWARE_API_TOKEN=<YOUR_LEXWARE_API_TOKEN>" --transport stdio lexware -- npx -y @lazyants/lexware-mcp-serverRequires: LEXWARE_API_TOKEN (secret)
Commands 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
The marketplaces of SnelStart MCP Server and API by Cotlet publish no settings it asks for, so we do not compare settings.
What it can do: SnelStart MCP Server and API by Cotlet · What it can do: io.github.lazyants/lexware · 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.