aria-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-roleA | Get detailed information about a specific ARIA role including its description, properties, states, required context, and accessibility requirements. |
| list-rolesB | List all ARIA roles, optionally filtered by category. Categories: widget, composite, document, landmark, liveRegion, window, abstract. |
| search-rolesA | Search for ARIA roles by keyword in their name or description. |
| get-attributeB | Get detailed information about an ARIA state or property (e.g., aria-label, aria-expanded, aria-hidden). |
| list-statesB | List all ARIA states with their descriptions. |
| list-propertiesB | List all ARIA properties. Optionally filter to show only global properties. |
| validate-role-attributesA | Validate which ARIA attributes are allowed, required, or prohibited for a specific role. |
| get-required-attributesC | Get all required ARIA attributes for a specific role. |
| get-prohibited-attributesC | Get all prohibited ARIA attributes for a specific role. |
| get-role-hierarchyB | Get the inheritance hierarchy for a role, showing parent and child roles. |
| get-required-contextC | Get the required parent context for a role (e.g., listitem requires list or group). |
| get-required-ownedB | Get the required child elements for a role (e.g., list requires listitem). |
| check-name-requirementsC | Check if a role requires an accessible name and how it can be provided. |
| get-roles-requiring-nameB | List all roles that require an accessible name. |
| list-landmarksB | List all ARIA landmark roles with guidance on their proper usage. |
| list-widget-rolesC | List all interactive widget roles that represent user interface controls. |
| list-live-regionsA | List all ARIA live region roles and explain their politeness levels. |
| get-aria-versionB | Get information about the ARIA specification version and metadata. |
| get-global-attributesB | List all global ARIA states and properties that apply to any element. |
| suggest-roleB | Suggest appropriate ARIA roles based on a description of the UI component. |
| get-server-infoB | Returns information about this MCP server. |
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 21 tools
Every tool has a clearly distinct purpose focused on specific aspects of ARIA (roles, attributes, validation, etc.). There is no overlap in functionality, with tools like get-role, get-attribute, and validate-role-attributes each serving unique but complementary purposes. The descriptions further clarify boundaries, making misselection unlikely.
Tool names follow a consistent verb_noun pattern throughout, using hyphens as separators (e.g., get-role, list-roles, validate-role-attributes). The verbs are predictable (get, list, check, search, suggest), and the nouns clearly indicate the target resource (role, attribute, landmarks). There are no deviations in naming conventions.
With 21 tools, the count is slightly high but reasonable for the comprehensive scope of ARIA accessibility, covering roles, attributes, validation, and guidance. Each tool earns its place by addressing specific queries, though some consolidation might be possible (e.g., multiple list-* tools). It supports thorough exploration without being overwhelming.
The toolset provides complete coverage of the ARIA domain, including CRUD-like operations (get, list, validate), hierarchical relationships (get-role-hierarchy), requirements (required attributes, context), and practical utilities (suggest-role, check-name-requirements). There are no obvious gaps; agents can handle all common ARIA-related tasks without dead ends.