MCP Server

The Model Context Protocol (MCP) is an open standard that lets AI agents call external tools in a structured, auditable way. Our hosted MCP server exposes the full Accessible Org toolset — PDF remediation, URL auditing, page-level fixes, and ACR scorecards — over a single secure endpoint. Point your agent at it once, and from then on your team can fix accessibility problems by asking, not by hand-clicking.

The marketing landing page lives at mcp.theaccessible.org.

What your agent can do

Four tools are exposed today. Every tool returns structured JSON so downstream agents and pipelines can act on it.

Tool	What it does
pdf-remediate	Convert a PDF into a tagged, WCAG-conformant accessible PDF + HTML report.
url-crawler	Crawl a page (or site) and return a structured accessibility audit.
url-remediate	Apply targeted fixes to an HTML page — alt text, ARIA, heading order, etc.
acr	Produce a vendor-grade ACR / VPAT 2.5 scorecard against WCAG 2.1 AA.

Each tool's input and output schema is published — your client will auto-discover them on connect.

Supported clients

• Claude Desktop
• Claude Code
• Cursor
• Windsurf
• VS Code (Copilot Chat)
• Any other MCP-compatible host

Prerequisites

• An MCP-capable client. If you are using Claude Desktop, version 0.10 or later. Other clients should be on a recent build that supports remote MCP servers over HTTP.
• An Accessible Org API key. Generate one at pdf.theaccessible.org/settings → API Keys → Create Key. Copy the key immediately — it is only shown once.

Connect in 60 seconds

Drop the snippet below into your client's MCP configuration. Replace with the key you just created.

{
"mcpServers": {
"accessible": {
"url": "https://api.theaccessible.org/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (or the equivalent on Windows) and paste the JSON above into the top-level mcpServers object. Quit and reopen Claude Desktop. The four tools above will be available the next time you open a chat.

Cursor / Windsurf

Both clients accept the same JSON via their settings UI. Look for MCP Servers under settings and add a new entry pointing at https://api.theaccessible.org/mcp.

Try it

Open a new chat in your client and ask:

Scan https://example.com for accessibility issues and tell me the top three things to fix.

The agent will pick url-crawler automatically, walk through the response, and answer in plain language. From there you can ask follow-ups like:

Generate an ACR for that scan.

Fix the alt-text issues you found and give me the updated HTML.

The agent will call acr or url-remediate as needed.

Authentication and rate limits

• The API key in the Authorization: Bearer header is the only thing the server needs to identify your account.
• Tool calls charge against your normal credit balance — there is no separate MCP pricing.
• Heavy operations (full-site crawls, PDF remediation) run asynchronously. The tool returns a job ID; the agent polls until it completes. Most jobs finish in 10–60 seconds.

Limitations

• One server, many tools. Tools are added centrally — you cannot publish your own tools through our endpoint. Use a local MCP server for that.
• No streaming responses. Each tool call returns a single JSON payload. If you need progress updates during a long crawl, poll the status field.
• Public web only by default. To scan pages behind a login, pass cookies or headers through url-crawler's auth argument (your agent will prompt you).

Troubleshooting

The client says "MCP server failed to start."

Almost always an unreachable or wrong URL. Confirm https://api.theaccessible.org/mcp resolves and that your Authorization header is present.

Tools list is empty after connecting.

Check that the API key is valid. Open pdf.theaccessible.org/settings and verify the key has not been rotated or revoked.

A tool call fails with 429.

You have hit a rate limit. Wait 60 seconds and retry, or contact support to raise your account limits.

Where to go from here

• The API reference documents every tool's input and output schema in detail — useful when you want to call the same operations directly from code.
• The Claude Desktop Skill guide describes an alternative integration that bundles the same tools as a downloadable extension.
• For pull-request-time auditing, see the CI/CD integration guide.