accessflow-mcp-server 2.3.4 → 2.3.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +107 -50
- package/dist/services/apiSchemas.d.ts +489 -1181
- package/dist/services/apiSchemas.d.ts.map +1 -1
- package/dist/services/apiSchemas.js +20 -9
- package/dist/services/apiSchemas.js.map +1 -1
- package/dist/services/apiService.d.ts +2 -1
- package/dist/services/apiService.d.ts.map +1 -1
- package/dist/services/apiService.js +24 -1
- package/dist/services/apiService.js.map +1 -1
- package/dist/tools/getIssueRemediation.d.ts +1 -5
- package/dist/tools/getIssueRemediation.d.ts.map +1 -1
- package/dist/tools/getIssueRemediation.js +1 -1
- package/dist/tools/getIssueRemediation.js.map +1 -1
- package/dist/tools/getMostUrgentIssues.js +8 -2
- package/dist/tools/getMostUrgentIssues.js.map +1 -1
- package/dist/tools/index.d.ts.map +1 -1
- package/dist/tools/index.js +5 -0
- package/dist/tools/index.js.map +1 -1
- package/dist/tools/resolveIssue.d.ts +1 -5
- package/dist/tools/resolveIssue.d.ts.map +1 -1
- package/dist/tools/resolveIssue.js +29 -5
- package/dist/tools/resolveIssue.js.map +1 -1
- package/dist/tools/submitFeedback.d.ts +7 -12
- package/dist/tools/submitFeedback.d.ts.map +1 -1
- package/dist/tools/submitFeedback.js +49 -37
- package/dist/tools/submitFeedback.js.map +1 -1
- package/dist/tools/toolRegistry.d.ts +11 -11
- package/dist/tools/toolRegistry.d.ts.map +1 -1
- package/dist/tools/toolRegistry.js +2 -0
- package/dist/tools/toolRegistry.js.map +1 -1
- package/dist/types/issues.d.ts +6 -0
- package/dist/types/issues.d.ts.map +1 -1
- package/dist/utils/remediation.d.ts.map +1 -1
- package/dist/utils/remediation.js +18 -4
- package/dist/utils/remediation.js.map +1 -1
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -2,61 +2,36 @@
|
|
|
2
2
|
|
|
3
3
|
# AccessFlow MCP Server
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
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.
|
|
6
6
|
|
|
7
|
-
##
|
|
7
|
+
## Purpose
|
|
8
8
|
|
|
9
9
|
The accessFlow MCP Server enables AI clients (like Copilot) to:
|
|
10
10
|
|
|
11
|
-
- **Identify
|
|
12
|
-
- **Provide
|
|
13
|
-
- **WCAG
|
|
14
|
-
- **Streamline
|
|
11
|
+
- **Identify priority issues**: Get the most urgent accessibility issues, ordered by severity and impact.
|
|
12
|
+
- **Provide fix guidance**: Generate detailed remediation instructions with code examples.
|
|
13
|
+
- **Align with WCAG**: Reference specific WCAG guidelines and criteria for each issue.
|
|
14
|
+
- **Streamline workflow**: Get detailed accessibility insights and fix recommendations directly in your IDE.
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## API Key Setup
|
|
17
17
|
|
|
18
|
-
|
|
18
|
+
Generate a token in accessFlow to set the API key.
|
|
19
19
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
1. **Severity**: EXTREME → HIGH → MEDIUM → LOW
|
|
23
|
-
2. **Site Impact**: Number of locations affected across the site
|
|
24
|
-
3. **Page Impact**: Number of occurrences on individual pages
|
|
25
|
-
|
|
26
|
-
**Parameters**: None (uses configured domain)
|
|
27
|
-
|
|
28
|
-
**Returns**: JSON data with structured issue information including severity, WCAG level, occurrence counts, and unique identifiers.
|
|
29
|
-
|
|
30
|
-
### `getIssueRemediation`
|
|
31
|
-
|
|
32
|
-
Provides detailed remediation guidance for a specific accessibility issue.
|
|
33
|
-
|
|
34
|
-
**Parameters**:
|
|
35
|
-
|
|
36
|
-
- `issueDisplayName` (string, required): The unique identifier for the accessibility issue
|
|
37
|
-
|
|
38
|
-
**Returns**: Comprehensive fix guidance including:
|
|
39
|
-
|
|
40
|
-
- Problem summary and WCAG references
|
|
41
|
-
- Current problematic code
|
|
42
|
-
- Suggested code fixes with examples
|
|
43
|
-
- Step-by-step remediation instructions
|
|
44
|
-
- Links to tutorials and additional resources
|
|
45
|
-
|
|
46
|
-
### `resolveIssue`
|
|
20
|
+
**To generate a token:**
|
|
47
21
|
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
**
|
|
22
|
+
1. Go to your **Profile** menu in the top right corner and select **Token management**.
|
|
23
|
+
2. Select **Generate token**.
|
|
24
|
+
3. Enter a token name.
|
|
25
|
+
4. Select **AI MCP token** and then **Generate token**.
|
|
26
|
+
5. Copy the token and store it securely. You won't be able to see it again.
|
|
52
27
|
|
|
53
|
-
|
|
28
|
+
## Configuration
|
|
54
29
|
|
|
55
|
-
|
|
30
|
+
Add the configuration to your MCP client (this varies by client), usually in the file `mcp.json`.
|
|
56
31
|
|
|
57
|
-
###
|
|
32
|
+
### Configure the accessFlow MCP server locally
|
|
58
33
|
|
|
59
|
-
|
|
34
|
+
Enter your copied token into `API_KEY`:
|
|
60
35
|
|
|
61
36
|
```json
|
|
62
37
|
{
|
|
@@ -76,29 +51,111 @@ Add the following configuration to your MCP client (e.g., VS Code Copilot Agent)
|
|
|
76
51
|
|
|
77
52
|
#### Configuration Parameters
|
|
78
53
|
|
|
79
|
-
|
|
80
|
-
|
|
54
|
+
| Parameter | Required | Description |
|
|
55
|
+
|-----------|----------|-------------|
|
|
56
|
+
| `API_KEY` | Yes | Your accessFlow API key for authentication |
|
|
57
|
+
| `DOMAIN` | Yes | The domain of your application being analyzed (e.g., `https://example.com`) |
|
|
58
|
+
|
|
59
|
+
### Connect to the accessFlow MCP server remotely
|
|
60
|
+
|
|
61
|
+
Connect remotely to the accessFlow MCP server: `flow-mcp.accessibe.com`
|
|
62
|
+
|
|
63
|
+
```json
|
|
64
|
+
{
|
|
65
|
+
"mcpServers": {
|
|
66
|
+
"flow-mcp": {
|
|
67
|
+
"type": "http",
|
|
68
|
+
"url": "https://flow-mcp.accessibe.com/mcp",
|
|
69
|
+
"headers": {
|
|
70
|
+
"Authorization": "Bearer <FLOW_MCP_API_KEY>",
|
|
71
|
+
"X-Domain": "mysite.com"
|
|
72
|
+
}
|
|
73
|
+
}
|
|
74
|
+
}
|
|
75
|
+
}
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
#### Configuration Parameters
|
|
79
|
+
|
|
80
|
+
| Parameter | Required | Description |
|
|
81
|
+
|-----------|----------|-------------|
|
|
82
|
+
| `Authorization` | Yes | Your accessFlow bearer token and API key for authentication |
|
|
83
|
+
| `X-Domain` | Yes | The domain of your application being analyzed (e.g., `https://example.com`) |
|
|
84
|
+
|
|
85
|
+
## MCP Server Commands
|
|
86
|
+
|
|
87
|
+
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.
|
|
81
88
|
|
|
82
|
-
###
|
|
89
|
+
### Get most urgent issues
|
|
83
90
|
|
|
84
|
-
|
|
91
|
+
#### `getMostUrgentIssues`
|
|
92
|
+
|
|
93
|
+
Retrieves the most critical accessibility issues, prioritized by:
|
|
94
|
+
|
|
95
|
+
1. **Severity**: Extreme → High → Medium → Low
|
|
96
|
+
2. **Site impact**: Number of locations affected across the site
|
|
97
|
+
3. **Page impact**: Number of occurrences on individual pages
|
|
98
|
+
|
|
99
|
+
**Parameters**: None (uses the configured domain)
|
|
100
|
+
|
|
101
|
+
**Returns**: JSON data with structured issue information including severity, WCAG level, occurrence counts, and unique identifiers.
|
|
85
102
|
|
|
86
|
-
**
|
|
103
|
+
**Example**:
|
|
87
104
|
|
|
88
105
|
```text
|
|
89
106
|
"Show me the most urgent accessibility issues for my site"
|
|
90
107
|
```
|
|
91
108
|
|
|
92
|
-
|
|
109
|
+
### Get issue remediation guidance
|
|
110
|
+
|
|
111
|
+
#### `getIssueRemediation`
|
|
112
|
+
|
|
113
|
+
Provides detailed remediation guidance for a specific accessibility issue.
|
|
114
|
+
|
|
115
|
+
**Parameters**:
|
|
116
|
+
|
|
117
|
+
| Parameter | Type | Required | Description |
|
|
118
|
+
|-----------|------|----------|-------------|
|
|
119
|
+
| `issueDisplayName` | string | Yes | The unique identifier for the accessibility issue |
|
|
120
|
+
|
|
121
|
+
**Returns**: Comprehensive fix guidance including:
|
|
122
|
+
|
|
123
|
+
- Problem summary and WCAG references
|
|
124
|
+
- Current problematic code
|
|
125
|
+
- Suggested code fixes with examples
|
|
126
|
+
- Step-by-step remediation instructions
|
|
127
|
+
- Links to tutorials and additional resources
|
|
128
|
+
|
|
129
|
+
**Example**:
|
|
93
130
|
|
|
94
131
|
```text
|
|
95
132
|
"Get remediation guidance for issue: Decorative-Content-6d277a13ba"
|
|
96
133
|
```
|
|
97
134
|
|
|
135
|
+
### Mark an issue as resolved
|
|
136
|
+
|
|
137
|
+
#### `resolveIssue`
|
|
138
|
+
|
|
139
|
+
Marks the specified issue as resolved in accessFlow.
|
|
140
|
+
|
|
141
|
+
> **Note:** If the next audit still detects this issue, it will be reopened automatically.
|
|
142
|
+
|
|
143
|
+
**Parameters**:
|
|
144
|
+
|
|
145
|
+
| Parameter | Type | Required | Description |
|
|
146
|
+
|-----------|------|----------|-------------|
|
|
147
|
+
| `issueDisplayName` | string | Yes | The unique identifier for the accessibility issue |
|
|
148
|
+
|
|
149
|
+
**Example**:
|
|
150
|
+
|
|
151
|
+
```text
|
|
152
|
+
"Resolve issue id Footer-Landmark-e3c792e8b8"
|
|
153
|
+
```
|
|
154
|
+
|
|
98
155
|
## Supported Clients
|
|
99
156
|
|
|
100
157
|
This MCP server works with AI agents in IDEs and other MCP-compatible clients:
|
|
101
158
|
|
|
102
|
-
- **VS Code Copilot**: Integrates with
|
|
159
|
+
- **VS Code Copilot**: Integrates with Microsoft Copilot in VS Code
|
|
103
160
|
- **Cursor**: Works with Cursor's AI assistant
|
|
104
161
|
- **Other MCP Clients**: Any application supporting the Model Context Protocol
|