Ext Ops Panel
Open dashboard
Comparison

Xero vs io.github.ar-agents/mcp

Xero is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.ar-agents/mcp is an MCP server published by ar-agents. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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.ar-agents/mcp
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 086
Stars (GitHub): 11 186
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.11
Downloads/month (npm): 572
Downloads/week (npm): 101
Forks (GitHub): 0
Stars (GitHub): 1
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.ar-agents/mcp
FactXeroio.github.ar-agents/mcp
Marketplaces that list it11
Stars (GitHub) (differs)11 186 (better)1 (worse)
Forks (GitHub) (differs)1 086 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@xeroapi/xero-mcp-server)On your machine (@ar-agents/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 4
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/ar-agents/ar-agents
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.ar-agents/mcp

In its own words, on Official MCP Registry:

Argentine business automation: Mercado Pago, AFIP/ARCA, WhatsApp, banking, shipping (7 packages).

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.ar-agents/mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "AFIP_CERT_PEM=<YOUR_AFIP_CERT_PEM>" --env "AFIP_KEY_PEM=<YOUR_AFIP_KEY_PEM>" --env "MP_ACCESS_TOKEN=<YOUR_MP_ACCESS_TOKEN>" --env "WHATSAPP_ACCESS_TOKEN=<YOUR_WHATSAPP_ACCESS_TOKEN>" --transport stdio io-github-ar-agents-mcp -- npx -y @ar-agents/mcp

Requires: AFIP_CERT_PEM (secret), AFIP_KEY_PEM (secret), MP_ACCESS_TOKEN (secret), WHATSAPP_ACCESS_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

Only Xero asks for

  • XERO_CLIENT_ID
  • XERO_CLIENT_SECRET (secret)

Only io.github.ar-agents/mcp asks for

  • AFIP_CERT_PEM (secret)
  • AFIP_CUIT
  • AFIP_KEY_PEM (secret)
  • MP_ACCESS_TOKEN (secret)
  • WHATSAPP_ACCESS_TOKEN (secret)
  • WHATSAPP_PHONE_NUMBER_ID

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.ar-agents/mcp · 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