helloasso-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELLOASSO_ENV | No | HelloAsso environment: sandbox or production. | sandbox |
| HELLOASSO_ORG_SLUG | No | Default organization slug, e.g. my-association. | |
| HELLOASSO_CLIENT_ID | Yes | Your HelloAsso API Client ID. | |
| HELLOASSO_CLIENT_SECRET | Yes | Your HelloAsso API Client Secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helloasso_get_organizationA | Public details of a HelloAsso organization (name, description, address, logo, URLs...). |
| helloasso_list_my_organizationsA | Organizations the API client has rights on (useful to find the organization slug). |
| helloasso_list_form_typesB | Form (campaign) types for which the organization has at least one form. |
| helloasso_list_formsA | List the organization forms (campaigns): memberships, events, donations, shops, crowdfunding, payment forms. Newest first, paginated. |
| helloasso_get_formA | Public details of one form: title, dates, tiers (prices), custom fields, state, URL. |
| helloasso_get_form_statsB | Statistics of one form (amounts collected, number of orders/items...). |
| helloasso_list_ordersA | List orders of the organization, or of one form when formType + formSlug are given. Supports date range, search and pagination. |
| helloasso_list_paymentsB | List payments of the organization, or of one form when formType + formSlug are given. Supports date range, payment states, search, sorting and pagination. |
| helloasso_list_itemsB | List items sold by the organization or by one form (formType + formSlug): e.g. the members of a membership campaign or the participants of an event, with custom fields answers. |
| helloasso_get_orderA | Detailed order by id: payer, items, payments, amounts. |
| helloasso_get_paymentA | Detailed payment by id: amount, state, payer, order, refund operations. |
| helloasso_get_itemA | Detailed item (one membership, ticket, donation...) by id, with custom fields. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct resource+action: organizations, form types, forms, form stats, items, orders, payments each have clear list/get boundaries. The list-vs-get distinction is unambiguous, and helloasso_list_my_organizations vs helloasso_get_organization is disambiguated by the descriptions (access rights vs public details).
Every tool follows the same helloasso_<verb>_<noun> pattern in consistent snake_case, with predictable list/get pairs. No mixing of conventions or vague verbs.
12 tools is well within the ideal range and each earns its place: list/get coverage across orgs, forms, items, orders, payments, plus form-types and stats helpers. No redundancy.
Full read/list lifecycle coverage for the domain (orgs, forms, items, orders, payments, stats) with no obvious list/get dead ends. Minor gaps: no create/update/delete or refund-initiation tool, though the server appears intentionally read-only and get_payment references refund operations it cannot act on.