Ext Ops Panel
Open dashboard
Comparison

Xero vs io.github.yuens1002/bookie

Xero is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.yuens1002/bookie is an MCP server published by yuens1002. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceXeroio.github.yuens1002/bookie
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 158
Stars (GitHub): 11 894
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.5
Downloads/month (npm): 448
Downloads/week (npm): 28
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

Xero vs io.github.yuens1002/bookie
FactXeroio.github.yuens1002/bookie
Marketplaces that list it11
Stars (GitHub) (differs)11 894 (better)0 (worse)
Forks (GitHub) (differs)1 158 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@xeroapi/xero-mcp-server)On your machine (bookie-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 13, secrets among them: 3
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/yuens1002/bookie
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Cursor: cursor/plugins:

Read and write invoices, contacts, reports, and payroll.

io.github.yuens1002/bookie

In its own words, on Official MCP Registry:

Double-entry bookkeeping MCP server — import bank CSVs, categorize, reconcile, tax reports.

How to run each

Xero

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.yuens1002/bookie As a local MCP server: npm package

Claude Code
claude mcp add --env "BOOKIE_API_KEY=<YOUR_BOOKIE_API_KEY>" --env "BOOKIE_DB_DIRECT_URL=<YOUR_BOOKIE_DB_DIRECT_URL>" --env "BOOKIE_DB_URL=<YOUR_BOOKIE_DB_URL>" --transport stdio bookie -- npx -y bookie-mcp

Requires: BOOKIE_API_KEY (secret), BOOKIE_DB_DIRECT_URL (secret), BOOKIE_DB_URL (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_ID
  • XERO_CLIENT_SECRET (secret)

Only io.github.yuens1002/bookie asks for

  • BOOKIE_API_KEY (secret)
  • BOOKIE_DB_DIRECT_URL (secret)
  • BOOKIE_DB_URL (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Xero · What it can do: io.github.yuens1002/bookie · 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.

Where the data comes from: how the catalog is built