What is the key difference between Google Surf Mcp and Mcp Accessibility Scanner?

Google Surf Mcp belongs to the Browser Automation category with local stdio execution, while Mcp Accessibility Scanner belongs to the Browser Automation category with local stdio execution.

How do I install Google Surf Mcp or Mcp Accessibility Scanner 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 Google Surf Mcp and Mcp Accessibility Scanner free or paid?

Google Surf Mcp operates under a Free / Open Source model (No auth required). Mcp Accessibility Scanner operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Google Surf Mcp lists 20 tools with 0 views and 277 GitHub stars. Mcp Accessibility Scanner lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Google Surf Mcp and Mcp Accessibility Scanner 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.

How do I install Google Surf Mcp or Mcp Accessibility Scanner in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Google Surf Mcp and Mcp Accessibility Scanner free to use, or do they require API keys?

Google Surf Mcp is listed under a Free / Open Source model with No auth required . Mcp Accessibility Scanner operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Google Surf Mcp and Mcp Accessibility Scanner at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both google-surf-mcp and mcp-accessibility-scanner as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Google Surf Mcp has a Quality Score of 61 /100 ( Good ) with 0 views, 0 installs, and 277 GitHub stars. Mcp Accessibility Scanner holds a Quality Score of 31 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Google Surf Mcp vs Mcp Accessibility Scanner

In-depth architectural comparison of the Google Surf Mcp and Mcp Accessibility Scanner 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

Google Surf Mcp

Browser Automation · Local stdio

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

Mcp Accessibility Scanner

Browser Automation · Local stdio

Quality: 31/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Google Surf Mcp if you need specialized Browser Automation tools running via a local process. Choose Mcp Accessibility Scanner 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 Google Surf Mcp 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: dropped, dropped_reasons, liteparse.

Explore Google Surf Mcp Details

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).

Explore Mcp Accessibility Scanner Details

Feature & Specification Comparison

Specification	G Google Surf Mcp Browser Automation	M Mcp Accessibility Scanner Browser Automation
Summary	Google search via Playwright with a warm Chrome profile. No API key, no proxies.	MCP server for automated web accessibility scanning with Playwright and Axe-core.
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Google Surf Mcp Tools (20)

dropped

dropped_reasons

liteparse

content

title

excerpt

length

is_pdf

page_count

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).

Google Surf Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "google-surf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-surf-mcp"
      ]
    }
  }
}

Mcp Accessibility Scanner Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Google Surf Mcp More alternatives to Mcp Accessibility Scanner Browser Automation category hub