HelloAsso vs io.github.erpipe-org/mcp-odoo
HelloAsso is an MCP server published by edouard-claude. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.erpipe-org/mcp-odoo is an MCP server published by erpipe-org. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-11. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (PyPI): 3 241 Downloads/week (PyPI): 2 241 Forks (GitHub): 198 Stars (GitHub): 431 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.3.0 Downloads/month (PyPI): 3 241 Downloads/week (PyPI): 2 241 Forks (GitHub): 198 Stars (GitHub): 431 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 | HelloAsso | io.github.erpipe-org/mcp-odoo |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 431 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 198 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/edouard-claude/helloasso-mcp:0.1.1) | On your machine (odoo-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/edouard-claude/helloasso-mcp | github.com/erpipe-org/mcp-odoo |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 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
HelloAsso
HelloAsso for associations: members, tickets, donations, payments, refunds, checkouts.
io.github.erpipe-org/mcp-odoo
Odoo MCP: gated writes, multi-instance. Free hosted: ERPipe (mcp.erpipe.com)
How to run each
HelloAsso As a local MCP server: Docker image
claude mcp add --env "HELLOASSO_CLIENT_ID=<YOUR_HELLOASSO_CLIENT_ID>" --env "HELLOASSO_CLIENT_SECRET=<YOUR_HELLOASSO_CLIENT_SECRET>" --transport stdio helloasso-mcp -- docker run -i --rm -e HELLOASSO_CLIENT_ID -e HELLOASSO_CLIENT_SECRET ghcr.io/edouard-claude/helloasso-mcp:0.1.1
Requires: HELLOASSO_CLIENT_ID, HELLOASSO_CLIENT_SECRET (secret)
io.github.erpipe-org/mcp-odoo As a local MCP server: PyPI package
claude mcp add --env "ODOO_DB=<YOUR_ODOO_DB>" --env "ODOO_PASSWORD=<YOUR_ODOO_PASSWORD>" --env "ODOO_URL=<YOUR_ODOO_URL>" --env "ODOO_USERNAME=<YOUR_ODOO_USERNAME>" --transport stdio mcp-odoo -- uvx odoo-mcp
Requires: ODOO_DB, ODOO_PASSWORD (secret), ODOO_URL, ODOO_USERNAME
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 HelloAsso asks for
HELLOASSO_CLIENT_IDHELLOASSO_CLIENT_SECRET (secret)HELLOASSO_ENVIRONMENTHELLOASSO_ORGANIZATIONHELLOASSO_READ_ONLY
Only io.github.erpipe-org/mcp-odoo asks for
ODOO_DBODOO_PASSWORD (secret)ODOO_URLODOO_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HelloAsso · What it can do: io.github.erpipe-org/mcp-odoo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.