Skip to main content
Glama
jbuchan

Accessibility MCP Server

by jbuchan

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
test_accessibilityB

Run accessibility tests on a website using Playwright and axe-core against WCAG standards

get_test_resultsC

Retrieve saved accessibility test results by filename

list_test_resultsB

List all available accessibility test result files

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_test_results retrieves specific results, list_test_results lists available files, and test_accessibility runs new tests. There is no overlap or ambiguity between these three functions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_test_results, list_test_results, test_accessibility) with clear, descriptive names that align with their actions. There are no deviations in naming conventions.

Tool Count4/5

With 3 tools, the server is well-scoped for its accessibility testing domain, covering core operations: listing, retrieving, and running tests. It might benefit from additional tools like updating or deleting results, but the count is reasonable and not excessive.

Completeness4/5

The tools provide a solid foundation for accessibility testing, covering listing, retrieval, and execution. Minor gaps exist, such as the inability to update or delete test results, but agents can work around this, and the core workflow is adequately supported.

Maintenance

ActivityInactive
ResponsivenessNo issues