Connect AI clients to accessFlow with an MCP server to find urgent accessibility issues, get WCAG-based guidance, and streamline remediation.
Overview
The accessFlow Model Context Protocol (MCP) server provides intelligent accessibility issue analysis and remediation guidance. It connects AI clients to the accessFlow platform to help developers identify, prioritize, and fix accessibility issues in their web applications.
The accessFlow MCP Server enables AI clients (like Copilot) to:
- Identify priority issues: Get the most urgent accessibility issues, ordered by severity and impact.
- Provide fix guidance: Generate detailed remediation instructions with code examples.
- Align with WCAG: Reference specific WCAG guidelines and criteria for each issue.
- Streamline workflow: Get detailed accessibility insights and fix recommendations directly in your IDE.
The accessFlow MCP server works with both platform audits and SDK-based audits. You can use it to analyze issues from your live site or connect it to SDK audit results.
API key setup
Generate a token in accessFlow to to set the API key.
To generate a token
- Go to your Profile menu in top right corner and select Token management.
- Select Generate token.
- Enter a token name.
- Select AI MCP token and then Generate token.
- Copy the token and store it securely. You won't be able to see it again.
Configuration
Add the configuration to your MCP client (this varies by client), usually in the file mcp.json.
Configure the accessFlow MCP server locally
Enter your copied token into API_KEY:
{
"mcpServers": {
"flow-mcp": {
"command": "npx",
"args": ["-y", "accessflow-mcp-server"],
"env": {
"API_KEY": "your-accessflow-api-key",
"DOMAIN": "<https://your-app-domain.com>"
},
"type": "stdio"
}
}
}Configuration parameters
| Parameter | Required | Description |
|---|---|---|
| API_KEY | Yes | Your accessFlow API key for authentication |
| DOMAIN | Yes | The domain of your application being analyzed (e.g., https://example.com) |
Connect to the accessFlow MCP server remotely
Connect remotely to the accessFlow MCP server: flow-mcp.accessibe.com
"flow-mcp": {
"type": "http",
"url": "<https://flow-mcp.accessibe.com/mcp>",
"headers": {
"Authorization": "Bearer <FLOW_MCP_API_KEY>",
"X-Domain": "mysite.com",
}
Configuration parameters
| Parameter | Required | Description |
|---|---|---|
| Authorization | Yes | Your accessFlow bearer token and API key for authentication |
| X-DOMAIN | Yes | The domain of your application being analyzed (e.g., https://example.com |
MCP server commands
Once configured, you can run commands through your MCP client to identify accessibility issues and get remediation guidance. You can use natural language or the command name.
Get most urgent issues
getMostUrgentIssues
Retrieves the most critical accessibility issues, prioritized by:
- Severity: Extreme → High → Medium → Low
- Site impact: Number of locations affected across the site
- Page impact: Number of occurrences on individual pages
You can run this command on either a platform audit or an SDK audit by setting the auditSource parameter.
Parameters
Uses the configured domain.
| Parameter | Type | Required | Description |
|---|---|---|---|
| auditSource | enum | no | Platform (default): Returns the most critical issues from the latest accessFlow platform audit. SDK: Returns the most critical issues from the specified SDK audit. Use either Platform or SDK. |
| commitId | string | required when auditSource=SDK | The commitID for the SDK audit results you want to retrieve. |
| repo | string | no | The repository name for the SDK audit. |
| branch | string | no | The branch name for the SDK audit. |
Returns
JSON data with structured issue information including severity, WCAG level, occurrence counts, and unique identifiers.
Example
"Show me the most urgent accessibility issues for my site"
Get issue remediation guidance
getIssueRemediation
Provides detailed remediation guidance for a specific accessibility issue. You can retrieve guidance from either a platform audit or an SDK audit by setting the auditSource parameter.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| issueDisplayName | string | Yes | The unique identifier for the accessibility issue. |
| auditSource | enum | no | Platform (default): Gets the issue guidance from the latest accessFlow platform audit. SDK: Gets the issue guidance from the specified SDK audit. Use either Platform or SDK. |
| commitId | string | required when auditSource=SDK | The commitID for the SDK audit results you want to retrieve. |
Returns
Comprehensive fix guidance including:
- Problem summary and WCAG references
- Current problematic code
- Suggested code fixes with examples
- Step-by-step remediation instructions
- Links to tutorials and additional resources
Example
"Get remediation guidance for issue: Decorative-Content-6d277a13ba"
Mark an issue as resolved
resolveIssue
Marks the specified issue as resolved in accessFlow.
Note: If the next audit still detects this issue, it will be reopened automatically.
You can resolve issues in either a platform audit or an SDK audit by setting the auditSource parameter.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| issueDisplayName | string | Yes | The unique identifier for the accessibility issue. |
| auditSource | enum | no | Platform (default): Resolve the issue in the accessFlow platform. SDK: Resolve the issue in the specified SDK audit. Use either Platform or SDK. |
| commitId | string | required when auditSource=SDK | The commitID for the SDK audit results you want to retrieve. |
Example
"Resolve issue id Footer-Landmark-e3c792e8b8"leSupported clients
This MCP server works with AI agents in IDEs and other MCP-compatible clients:
- VS Code Copilot: Integrates with Microsoft Copilot in VS Code
- Cursor: Works with Cursor's AI assistant
- Other MCP Clients: Any application supporting the Model Context Protocol