What is the key difference between MCP Accessibility Scanner and MCP Browser Agent?

MCP Accessibility Scanner belongs to the Browser Automation category with local stdio execution, while MCP Browser Agent belongs to the Browser Automation category with local stdio execution.

How do I install MCP Accessibility Scanner or MCP Browser Agent in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Accessibility Scanner and MCP Browser Agent free or paid?

MCP Accessibility Scanner operates under a Free / Open Source model (No auth required). MCP Browser Agent operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Accessibility Scanner lists 42 tools with 0 views and 56 GitHub stars. MCP Browser Agent lists 12 tools with 3 views and 41 GitHub stars.

Can I use both MCP Accessibility Scanner and MCP Browser Agent together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Accessibility Scanner vs MCP Browser Agent

In-depth architectural comparison of the MCP Accessibility Scanner and MCP Browser Agent MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Accessibility Scanner

Browser Automation · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

MCP Browser Agent

Browser Automation · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose MCP Accessibility Scanner if you need specialized Browser Automation tools running via a local process. Choose MCP Browser Agent if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Accessibility Scanner when:

You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: scan_page, audit_site, scan_page_matrix.

Explore MCP Accessibility Scanner Details

Choose MCP Browser Agent when:

You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: MCP_BROWSER_TYPE.
Primary tools included: browser_navigate, browser_screenshot, browser_click.

Feature & Specification Comparison

Specification	MCP Accessibility Scanner Browser Automation	MCP Browser Agent imprvhub Browser Automation
Summary	MCP server for automated web accessibility scanning with Playwright and Axe-core.	A Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities.
Category & Scope	Browser Automation

Tools & Capabilities Breakdown

MCP Accessibility Scanner Tools (42)

scan_page

Performs a comprehensive accessibility scan on the current page using Axe-core.

audit_site

Crawls and scans multiple internal pages, then aggregates violations across the site.

scan_page_matrix

Runs Axe scans on the same page across viewport/media/zoom variants and compares deltas against baseline.

audit_keyboard

Audits real keyboard focus behavior by pressing Tab (and optional Shift+Tab) with practical heuristics.

audit_screen_reader

Audits what a screen reader actually announces, using the browser's own accessibility tree (`page.ariaSnapshot`) plus element geometry. No screen reader is installed or driven; this is a static reading of the exposed tree.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Accessibility Scanner Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-accessibility-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-accessibility-scanner"
      ]
    }
  }
}

MCP Browser Agent Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "imprvhub-mcp-browser-agent": {
      "command": "npx",
      "args": [
        "-y",
        "imprvhub-mcp-browser-agent"
      ],
      "env": {
        "MCP_BROWSER_TYPE": "YOUR_MCP_BROWSER_TYPE_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Accessibility Scanner is categorized under Browser Automation and uses a local stdio subprocess. In contrast, MCP Browser Agent belongs to Browser Automation using local stdio subprocess. Select MCP Accessibility Scanner when you need capabilities focused on browser automation and MCP Browser Agent when you require tools for browser automation.

More alternatives to MCP Accessibility Scanner More alternatives to MCP Browser Agent Browser Automation category hub Canonical compare URL