HelloAsso

mcp-helloasso

Your association's HelloAsso, answered by asking.

A single Rust binary that puts the whole HelloAsso v5 API — memberships, tickets, donations, payments, refunds, checkouts — in front of any MCP client.

🇫🇷 *Serveur MCP pour HelloAsso : adhérents, billetterie, dons, paiements et remboursements, interrogés en langage naturel depuis Claude, Cursor ou tout client MCP.*

Ask your assistant *"how much did we collect last month?"*, *"is Camille Martin's membership paid?"*, *"give me the attendee list of the gala"* — and get the answer from the same HelloAsso your treasurer reconciles against.

> how much did we collect in September, and on what?

summarize_payments 2026-09 · 214 payments read collected 8 342,00 € (196 authorized) Membership/adhesion-2026 5 160,00 € 61.9% Event/gala-2026 2 730,00 € 32.7% Donation/dons 452,00 € 5.4% by means: Card 7 912,00 € · Sepa 430,00 € refunded 60,00 € · 3 refused · 1 contested

who registered for the gala, with their dietary answers?

list_form_items form_url = helloasso.com/associations/les-amis-du-velo/evenements/gala-2026 item_states = Processed, Registered · with_details = true 87 participants, 3 tiers, custom field "Régime alimentaire"

Paste a HelloAsso URL, say *last month*, name a person. The server resolves the organization, the form, the period and the pagination.

Why

HelloAsso's API is a clean REST surface, but handing it raw to a language model goes wrong in predictable ways: amounts are cents, a form is a *(type, slug)* pair nobody remembers, date ranges are half-open, tokens expire every 30 minutes, and the one call that matters most — a refund — sends real money back with no undo.

• The whole API, nothing hidden. All 36 routes of the public v5 spec, one tool each, plus whoami and summarize_payments, which exist because the API has no "who am I" for a client and no aggregate. A test fails if that count ever drops.
• URLs, words and periods, not identifiers. Every form tool takes the form's public URL. Form types read in English, French or URL spelling (evenements, adhésions). Periods read last month, 2026-09, last 30 days. Persons are found with search.
• Money that adds up. summarize_payments walks every page and splits what was *actually* collected (Authorized) per form, payment means and month, in cents and euros — no model adding up page one and calling it a total.
• Fail-closed where money moves. refund_payment and cancel_order refuse to run without confirm: true, and the refusal states the amount and the payer so the confirmation is an informed one. HELLOASSO_READ_ONLY=1 withholds every write tool.
• OAuth handled the way HelloAsso asks. client_credentials once, then refresh_token — never a new grant while a refresh works, as the API requires. A token revoked server-side is renewed transparently.
• Written for a model to read. Structured output with schemas on all 38 tools, annotations on every one, four prompts that stop and ask before touching money, and server instructions that say up front: amounts are cents.

Install

Prebuilt binary (macOS, Linux, Windows)

Download the archive for your platform from the latest release, check it against its .sha256, and put mcp-helloasso on your PATH:

# macOS on Apple silicon; swap the target for x86_64-apple-darwin,

x86_64-unknown-linux-gnu or aarch64-unknown-linux-gnu

V=v0.1.1 T=aarch64-apple-darwin curl -LO https://github.com/edouard-claude/helloasso-mcp/releases/download/$V/mcp-helloasso-$V-$T.tar.gz tar xzf mcp-helloasso-$V-$T.tar.gz sudo mv mcp-helloasso-$V-$T/mcp-helloasso /usr/local/bin/

Windows: take the x86_64-pc-windows-msvc.zip archive.

From source (any platform with Rust 1.88+)

git clone https://github.com/edouard-claude/helloasso-mcp

cd helloasso-mcp cargo build --release

the binary is at target/release/mcp-helloasso

</details>

With cargo install

cargo install --git https://github.com/edouard-claude/helloasso-mcp

With Docker

docker run --rm -i \

-e HELLOASSO_CLIENT_ID=… -e HELLOASSO_CLIENT_SECRET=… \ ghcr.io/edouard-claude/helloasso-mcp:latest

Or build it yourself with docker build -t mcp-helloasso ..

The server is listed in the official MCP registry as io.github.edouard-claude/helloasso-mcp, so registry-aware clients offer it directly with the variables to fill in.

The image runs unprivileged and speaks stdio by default; add --http for the HTTP transport. See Run it over HTTP instead.

Get API credentials

In the HelloAsso back office of your association: My account → Integrations and API (*Mon compte → Intégrations et API*). You get a client id and a client secret, with the AccessPublicData, AccessTransactions and Checkout privileges, scoped to your organization. Partners get theirs from HelloAsso's partnership team.

Then check the wiring before pointing a client at it:

HELLOASSO_CLIENT_ID=… HELLOASSO_CLIENT_SECRET=… mcp-helloasso --check

environment  production

base url https://api.helloasso.com/v5 toolsets organization, forms, sales, checkout, directory, partner read only false tools 38 token ok reachable 1 organization(s) Les Amis du Vélo (les-amis-du-velo) as OrganizationAdmin organization Les Amis du Vélo (les-amis-du-velo)

ready.

Configure

Which organization. An association's client reaches exactly one organization, and the server finds it on its own. A partner client reaching several gets the list back as candidates; set HELLOASSO_ORGANIZATION or pass organization per call. The binary refuses to start on a malformed variable and names the one at fault.

Connect a client

Claude Code

claude mcp add helloasso --scope user \

--env HELLOASSO_CLIENT_ID=… \ --env HELLOASSO_CLIENT_SECRET=… \ -- /absolute/path/to/mcp-helloasso

</details>

Claude Desktop

claude_desktop_config.json:

{

"mcpServers": { "helloasso": { "command": "/absolute/path/to/mcp-helloasso", "env": { "HELLOASSO_CLIENT_ID": "…", "HELLOASSO_CLIENT_SECRET": "…", "HELLOASSO_READ_ONLY": "1" } } } }

Start read-only; lift it once you trust the setup.

Cursor, Windsurf, Zed, and other stdio clients

Same shape: one command pointing at the binary, the credentials in env. The server speaks the stdio transport and prints nothing but protocol on stdout — logs go to stderr.

Any client, over HTTP

Point it at http://127.0.0.1:8080/mcp after starting the server with --http 127.0.0.1:8080. See below.

Then ask *"which HelloAsso organization are you connected to?"*. whoami should answer with your association's name.

Tools

38 tools in six toolsets, covering the 36 routes of the public v5 spec. HELLOASSO_TOOLSETS picks which ones are registered; HELLOASSO_READ_ONLY=1 keeps only the ones that declare themselves read-only.

sales — orders, items, payments, the treasurer's view

forms — the campaigns

| list_form_types | `GET /organi