Cursor A11y 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| a11yB | Run accessibility tests on a URL or a local path (relative URL appended to http://localhost:5000). |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'a11y' has a clear and distinct purpose focused on accessibility testing.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'a11y' is concise and descriptive, and there are no other tools to compare it against for consistency.
A single tool is too few for a server named 'Cursor A11y MCP', which suggests a broader accessibility domain. While the tool is functional, the set lacks coverage for other common accessibility tasks like reporting, fixing issues, or checking compliance, making it feel thin and incomplete.
The tool surface is severely incomplete for an accessibility domain. It only provides testing on URLs or local paths, missing essential operations such as generating reports, analyzing results, fixing issues, or supporting different accessibility standards, which will limit agent effectiveness.