Ext Ops Panel
Open dashboard
Comparison

Xero vs io.github.singleflo/odoo-assistant

Xero is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.singleflo/odoo-assistant is an MCP server published by singleflo. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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.singleflo/odoo-assistant
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 107
Stars (GitHub): 11 352
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (PyPI): 200
Downloads/week (PyPI): 40
Forks (GitHub): 3
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.singleflo/odoo-assistant
FactXeroio.github.singleflo/odoo-assistant
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)11 352 (better)1 (worse)
Forks (GitHub) (differs)1 107 (better)3 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@xeroapi/xero-mcp-server)On your machine (odoo-assistant)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 17, secrets among them: 1
Parts of the bundle11
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/singleflo/odoo-assistant-mcp
Changes in the last 7 days (differs)02
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.singleflo/odoo-assistant

In its own words, on Official MCP Registry:

Odoo virtual employee via MCP: query, create, modify records, workflows, PDFs, and activities.

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.singleflo/odoo-assistant As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ODOO_API_KEY=<YOUR_ODOO_API_KEY>" --env "ODOO_BASE_URL=<YOUR_ODOO_BASE_URL>" --transport stdio odoo-assistant -- uvx odoo-assistant

Requires: ODOO_API_KEY (secret), ODOO_BASE_URL

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.singleflo/odoo-assistant asks for

  • ODOO_API_KEY (secret)
  • ODOO_BASE_URL
  • ODOO_DB
  • ODOO_MCP_ALLOW
  • ODOO_MCP_ALLOW_UNLINK
  • ODOO_MCP_DENY
  • ODOO_USER

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.singleflo/odoo-assistant · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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