ara-rgaa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARA_BASE_URL | No | URL de base de l'API Ara | https://ara.numerique.gouv.fr/api |
| ARA_PASSWORD | No | Mot de passe pour auto-login au démarrage | |
| ARA_USERNAME | No | Email pour auto-login au démarrage | |
| ARA_AUTH_TOKEN | No | Token JWT pré-configuré (évite le login) |
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 |
|---|---|
| auth_signinA | Authenticate to the Ara platform using email/password. Returns a JWT token that will be used for all subsequent requests. Required only if ARA_AUTH_TOKEN is not set. |
| create_auditA | Create a new RGAA accessibility audit in Ara. Returns the audit with its editUniqueId (for editing) and consultUniqueId (for viewing the report). Audit types:
|
| get_auditA | Retrieve a full audit by its editUniqueId. Returns all metadata, pages, environments, and notes. |
| update_auditC | Full update of an audit's metadata (procedure info, auditor info, environments, tools, technologies, notes, etc.). |
| patch_audit_notesA | Update only the notes field of an audit. Useful for adding audit observations without touching other metadata. |
| delete_auditA | Soft-delete an audit. The audit will return HTTP 410 Gone for future requests. |
| duplicate_auditA | Fully duplicate an existing audit (metadata, pages, RGAA results, example images). Returns a new audit with fresh IDs. |
| publish_auditA | Mark an audit as published/completed. The audit must be fully filled in (all criteria evaluated) before publishing. Returns HTTP 409 if incomplete. |
| get_audit_resultsA | Retrieve all criterion results for an audit. Returns an array of results, each with:
|
| update_audit_resultsA | Update criterion results for an audit. Send an array of result items. Each item targets one criterion on one page using (pageId, topic, criterium). The topic/criterium must be a valid RGAA combination. Topics 1-13:
Status values: COMPLIANT, NOT_COMPLIANT, NOT_APPLICABLE, NOT_TESTED User impact values: MINOR, MAJOR, BLOCKING |
| get_page_resultsA | Get criterion results for a specific page of an audit. The pageSlug is typically the page order number. |
| get_reportA | Get the full audit report (read-only). Includes accessibility rate, criteria counts, and result distributions by page and topic. Uses the consultUniqueId (not the editUniqueId). |
| update_statementB | Update the accessibility statement (déclaration d'accessibilité) for an audit. This is used to generate the public accessibility statement. |
| export_csvB | Export audit results in CSV format. |
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 14 tools
Each tool targets a distinct action within the audit lifecycle: authentication, CRUD for audits, result management, export, report generation, and statement updates. No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_audit, get_audit_results, update_statement). 'auth_signin' is slightly different but still fits the pattern. No mixing of styles.
14 tools cover the full scope of RGAA audit management: authentication, full CRUD, duplicate, publish, export, and result updates. This is well-scoped for the domain without being excessive or insufficient.
The tool set covers all major operations (create, read, update, delete, duplicate, publish, export, statement). A minor gap is the lack of a 'list_audits' tool to retrieve all audits, but core workflows are well-supported.