MagentaA11y MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MagentaA11y MCP Server get accessibility criteria for a web button component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MagentaA11y MCP Server
Provides accessibility acceptance criteria from MagentaA11y via MCP protocol.
Local: stdio transport for Claude Desktop, Cursor, VSCode
Remote: HTTP transport deployed to Netlify serverless functions
Parses markdown into content.json, loads into memory with Fuse.js search indices for <5ms responses. 11 tools covering 51 web + 42 native components.
Technology Stack
This MCP server uses Netlify Edge Functions to provide stateless HTTP transport, exposing MCP tools via JSON-RPC protocol at the /mcp endpoint. The netlify/functions/api.js handler implements the full MCP lifecycle—initialization, tool listing, and tool execution—while managing in-memory content loading and CORS. Clients connect using mcp-remote@next, an NPX-installable proxy that bridges the HTTP transport to MCP-compatible IDEs like VSCode, Claude Desktop, and Cursor. This architecture enables zero-config remote deployment: push to GitHub, connect to Netlify, and any MCP client can instantly access the tools via npx mcp-remote@next https://your-site.netlify.app/mcp.
Available Tools
Web: list_web_components, get_web_component, search_web_criteria
Native: list_native_components, get_native_component, search_native_criteria
Formats: get_component_gherkin, get_component_condensed, get_component_developer_notes, get_component_native_notes, list_component_formats
Quick Start
npm install && npm run buildLocal MCP: Configure IDE with stdio transport (see below)
Remote MCP: Deploy to Netlify for HTTP transport access
MCP Configuration
Add absolute path to build/index.js in your IDE config:
VSCode (Local)
File: %APPDATA%\Code\User\mcp.json
{
"MagentaA11y MCP": {
"type": "stdio",
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/magentaa11y-mcp/build/index.js"]
}
}VSCode (Remote - Netlify)
File: %APPDATA%\Code\User\mcp.json
{
"MagentaA11y MCP": {
"command": "npx",
"args": ["mcp-remote@next", "https://your-site.netlify.app/mcp"]
}
}Replace your-site.netlify.app with your actual Netlify deployment URL.
Restart IDE after configuration.
Commands
npm run build - Full buildnpm run sync - Update contentnpm start - Test MCP (stdio)
Deployment
Push to GitHub and connect to Netlify. The netlify.toml and netlify/functions/api.js are configured for stateless HTTP transport at /mcp endpoint.
Note: Remote MCP clients use mcp-remote@next proxy for maximum compatibility with the HTTP transport.
Resources
MagentaA11y • MCP • WCAG
License: MIT
Available Tools
11 toolsget_component_condensedB
Get condensed acceptance criteria for a component. These are shorter, more focused testing instructions.
Inputs: platform (required), component (required).
get_component_developer_notesB
Get developer implementation notes for a component. Includes code examples, WCAG mappings, and technical guidance.
Inputs: platform (required), component (required).
get_component_gherkinB
Get Gherkin-style acceptance criteria for a component. These are detailed Given/When/Then scenarios for testing accessibility.
Inputs: platform (required), component (required).
get_component_native_notesB
Get platform-specific developer notes for native components (iOS or Android implementation details).
Inputs: platform (required), component (required).
get_native_componentA
Get detailed accessibility criteria for a specific native component. Returns iOS and Android implementation details, platform-specific properties, and code examples.
Inputs: component (required), include_code_examples.
get_web_componentB
Get detailed accessibility criteria for a specific web component. Returns acceptance criteria, WCAG mappings, code examples, and implementation guidelines.
Inputs: component (required), include_code_examples.
list_component_formatsB
List all available content formats for a specific component (e.g., gherkin, condensed, developer notes).
Inputs: platform (required), component (required).
list_native_componentsA
List all available native (iOS/Android) accessibility components from MagentaA11y. Optionally filter by category.
Inputs: category.
list_web_componentsC
List all available web accessibility components from MagentaA11y. Optionally filter by category (e.g., controls, forms, components).
Inputs: category.
search_native_criteriaA
Search native accessibility criteria using keywords. Find platform-specific implementation details for iOS (VoiceOver) and Android (TalkBack).
Inputs: query (required), max_results.
search_web_criteriaB
Search web accessibility criteria using keywords. Find criteria related to WCAG guidelines, implementation patterns, or specific accessibility requirements.
Inputs: query (required), max_results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized by target platform (web vs. native) and action type (get details, list components, search criteria), making it easy for an agent to select the right tool for the task. For example, get_web_component retrieves detailed criteria for a specific web component, while search_web_criteria performs keyword searches across web criteria.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. The naming convention clearly indicates the action (get, list, search) and the target resource (component, criteria), with platform prefixes (web_ or native_) where applicable. This predictability makes the tool set easy to navigate and understand.
With 11 tools, the count is well-scoped for the server's purpose of providing accessibility criteria and components. Each tool earns its place by covering distinct aspects like retrieval, listing, and searching across web and native platforms, without redundancy. This number supports comprehensive functionality while remaining manageable.
The tool surface offers complete coverage for the accessibility domain, with no obvious gaps. It includes CRUD-like operations (get details, list components, search criteria) for both web and native platforms, along with specialized formats (condensed, developer notes, Gherkin). This ensures agents can handle various accessibility tasks without dead ends.
Related MCP Connectors
Accessible React components, tokens, usage guidance, and install commands for product interfaces.
Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.
Find UI components and themes, retrieve code, and generate with hosted 21st AI when enabled.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.