A11y Check vs Ui.Vision MCP

A side-by-side look at the A11y Check and Ui.Vision MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

A
A11y CheckBrowser Automation · Remote HTTP/SSE
Check a web page for accessibility problems in a real browser, with the code that fixes each one.42FairAuth: not declared
Ui.Vision MCP logoUi.Vision MCPBrowser Automation · Local subprocess (stdio)MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input52GoodAuth: not declared

Verdict: choose A11y Check for browser automation work over a hosted endpoint; choose Ui.Vision MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose A11y Check when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a remote HTTP/SSE transport.
Explore A11y Check

Ui.Vision MCP logoChoose Ui.Vision MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Ui.Vision MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
A11y Check
Ui.Vision MCP logoUi.Vision MCP
CategoryBrowser AutomationBrowser Automation
Quality signal42/100 · Fair52/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—2,087
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

A11y Check tools

No tool names declared yet. Check the project README from the listing page.

Ui.Vision MCP tools

No tool names declared yet. Check the project README from the listing page.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "a11y-check-2": {
      "url": "https://nexaaly.com/mcp"
    }
  }
}

Ui.Vision MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ui-vision-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "uivision-mcp-bridge"
      ]
    }
  }
}

Frequently asked questions

A11y Check is categorized under Browser Automation and uses a remote HTTP/SSE transport. Ui.Vision MCP belongs to Browser Automation and uses a local stdio subprocess. Pick A11y Check for browser automation work and Ui.Vision MCP for browser automation.

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.

A11y Check has no declared pricing — check the project's own site. Ui.Vision MCP has no declared pricing — check the project's own site. 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-2 and ui-vision-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 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Ui.Vision MCP has 52/100 (Good) with 2 views, 0 installs and 2,087 GitHub stars.