Xero vs mcp-newbuild
Xero is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). mcp-newbuild is an MCP server published by atomno-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  mcp-newbuild | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 197 Stars (GitHub): 12 306 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 Downloads/month (PyPI): 168 Downloads/week (PyPI): 53 Forks (GitHub): 0 Stars (GitHub): 0 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 | Xero | mcp-newbuild |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 306 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 197 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@xeroapi/xero-mcp-server) | On your machine (atomno-mcp-newbuild) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 2 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/atomno-mcp/mcp-newbuild |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Xero
Read and write invoices, contacts, reports, and payroll.
mcp-newbuild
New-build MCP on the client's EISZHS contract. Spec is closed.
How to run each
Xero
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
mcp-newbuild As a local MCP server: PyPI package
claude mcp add --env "MCP_NEWBUILD_API_KEY=<YOUR_MCP_NEWBUILD_API_KEY>" --env "MCP_NEWBUILD_EISZHS_CLIENT_SECRET=<YOUR_MCP_NEWBUILD_EISZHS_CLIENT_SECRET>" --transport stdio mcp-newbuild -- uvx atomno-mcp-newbuildRequires: MCP_NEWBUILD_API_KEY (secret), MCP_NEWBUILD_EISZHS_CLIENT_SECRET (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
Only Xero asks for
XERO_CLIENT_IDXERO_CLIENT_SECRET (secret)
Only mcp-newbuild asks for
MCP_NEWBUILD_API_KEY (secret)MCP_NEWBUILD_EISZHS_CLIENT_IDMCP_NEWBUILD_EISZHS_CLIENT_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Xero · What it can do: mcp-newbuild · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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.