Accessibility Tracker now has its own MCP server. This means you can connect your Tracker account directly to Claude and manage your accessibility projects by chatting with Claude.
(P.S. voice dictation makes it even easier to manage your project and check progress.)
MCP (Model Context Protocol) is the open standard AI assistants use to connect to outside tools and data. Once Tracker is connected, Claude can see your projects, read your issues, update them, and trigger scans. You never leave the chat.
In the next two weeks, we’ll also add ChatGPT.
Full WCAG conformance, not just a scan
This is what we keep harping on: most accessibility platforms are scan-based. Tracker is for full WCAG conformance (you have to have the manual evaluation as the foundation or else your entire project is completely skewed).
Stated another way, the issues Claude works through in Tracker are not limited to what an automated scanner can detect. Tracker projects hold the findings from a full accessibility audit against every WCAG success criterion, including the keyboard, screen reader, focus, and the many issues that automated tools cannot catch (or can only partially flag).
Other accessibility MCP servers on the market connect an AI agent to a scanner. That gets you a fraction of WCAG. Tracker’s MCP server connects Claude to the complete conformance picture for your site, so when you ask Claude what’s left to fix, the answer covers all of WCAG 2.2 AA, not an unknown subset of it.
What you can do
Once connected, you can ask Claude to:
See everything at a glance. List all of your projects, pull the details on any one of them, or ask how many issues are still open across your entire account.
Pull issues and fix them in the same place. If you’re working on custom code, ask Claude to pull the open issues for a project, work through the fixes with you, and then mark each one as resolved once you’ve verified it.
Update issues in bulk. Need to close out twenty issues across two projects? Say so. Claude updates them all in one pass. Bulk uploads and spreadsheet imports are no longer the only way to move a lot of issues at once.
Update project details. Change a project name, description, or other details without opening the portal.
Trigger a scan. Ask Claude to scan a site and Tracker starts the scan in the background.
Every AI action is logged
Everything Claude does through the MCP connection is recorded in your project activity, including bulk updates. If something changes, you can see exactly what the AI did and when. Nothing happens silently.
You control the access
When you connect, Tracker asks which projects Claude is allowed to touch. You can allow all current and future projects, or pick specific ones. Access can be revoked at any time from your Tracker settings.
How to connect
- Log in to Accessibility Tracker and open Settings.
- Under MCP Server, copy your connection URL.
- In Claude, go to Customize, then Connectors, then Add custom connector.
- Paste the URL and click Add.
- Click Connect, choose which projects to authorize, and click Authorize.
You’ll be sent back to Claude with Tracker connected and ready. If you prefer to authenticate with an API key instead, that option is available in the same settings panel, and keys can be revoked and regenerated whenever you want.
Works where you work
The MCP server works with Claude (web, desktop, and Claude Code), Cursor, Windsurf, VS Code, and any other client that supports MCP.
Again, ChatGPT is coming soon.
Chrome extension
If you missed it, the Tracker Chrome extension is already available. It lets you scan authenticated pages (pages behind a login) and sends the results straight back to your Tracker project. The extension uses the same API key system as the MCP server.
What’s next
VPAT and ACR support through MCP is on the roadmap. Project and issue management came first because that’s where the most time gets spent.
The MCP server rolls out to all Accessibility Tracker accounts the first week of September.
