Model Context Protocol

OverlayQA MCP Server

The OverlayQA MCP server brings design QA into your AI coding agent. From Claude Code, Cursor, Windsurf, or any MCP-compatible client, scan any URL for accessibility and design-system issues, then file and track dev-ready bugs straight into your OverlayQA projects without leaving the editor. The server runs over standard stdio and connects to your OverlayQA account on first run.

Install

Add the server to your editor's MCP config, or run it directly with npx @overlayqa/mcp@latest. The same config works in Claude Code (.mcp.json), Cursor (~/.cursor/mcp.json), and Windsurf (~/.codeium/windsurf/mcp_config.json).

{
  "mcpServers": {
    "overlayqa": { "command": "npx", "args": ["@overlayqa/mcp@latest"] }
  }
}

Tools your agent can call

Eight live tools, each written so the model picks the right one from natural language.

• scan_accessibility — Run a WCAG audit (axe-core) on any URL. Returns violations with severity, WCAG success criteria, and an overall score.
• scan_contrast — Check color-contrast ratios across a page. Returns the failing foreground and background element pairs.
• audit_tokens — Audit a page's design tokens for drift across spacing, typography, color, and border radius.
• scan_and_create_issues — Scan a URL and auto-create an issue for every violation above a severity threshold.
• create_issue — File a QA issue with title, severity, type, and description.
• list_issues — List issues in a project, filtered by status and severity.
• create_project — Create a project for a site URL.
• list_projects — List all projects on your team.

One more tool, compare_visual, is coming soon for Figma visual comparison.

How it works

Add the server to your editor, connect your OverlayQA account on first run (no card, token caches locally for 30 days), then scan and track the issues it finds. Everything lands in the same projects as the OverlayQA Chrome extension and dashboard, so issues stay in sync across surfaces.

Pricing

Free: 3 accessibility and contrast scans per day, forever. The 14-day trial raises that to 30 scans per day and unlocks issue and project creation. Paid plans run 10 to 30 scans per day, with unlimited scans on Pro and export to Linear, Jira, Asana, and Notion.

Frequently asked questions

Which editors does it work with? Claude Code, Cursor, Windsurf, and any MCP-compatible client. It speaks standard stdio MCP.

Is it free? Yes to start: 3 scans per day with no card. A 14-day trial raises that to 30 scans per day and unlocks issue and project creation.

Do I need an account? Yes, an OverlayQA account. On first run a browser tab opens to connect it, and the token caches locally for 30 days.

Last updated June 2026