A11y Check vs Inclusio MCP
A side-by-side look at the A11y Check and Inclusio MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
Inclusio MCPDeveloper ToolsInclusio MCP server for accessibility-first LaTeX publishing (PDF/UA-2, WTPDF, PDF/A-4f).47FairAuth: no auth requiredVerdict: choose A11y Check for browser automation work as a local process; choose Inclusio MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose A11y Check when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
IChoose Inclusio MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
INCLUSIO_CONTENT_DIR. - You want tools like
list_docs, doc_count, render.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Inclusio MCP | |
|---|---|---|
| Category | Browser Automation | Developer Tools |
| Quality signal | 41/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | INCLUSIO_CONTENT_DIR |
| Verified owner |
Tools & capabilities
A11y Check tools
No tool names declared yet. Check the project README from the listing page.
Inclusio MCP tools 4
list_docsEnumerate documents registered in the content treedoc_countQuick count of available documentsrenderBuild a tagged, conformant PDF (and other formats) for a documentaudit_pdfAccessibility audit of a PDF (veraPDF)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
A11y Check
{
"mcpServers": {
"a11y-check": {
"command": "npx",
"args": [
"-y",
"@a11ychk/mcp"
]
}
}
}
Inclusio MCP
No confirmed install command for Inclusio MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
A11y Check is categorized under Browser Automation and uses a local stdio subprocess. Inclusio MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick A11y Check for browser automation work and Inclusio MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Inclusio MCP has no confirmed install command yet — follow its own setup instructions.
A11y Check has no declared pricing — check the project's own site. Inclusio MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add a11y-check and inclusio-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, A11y Check has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. Inclusio MCP has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
