What is the key difference between Devilge and Google Surf Mcp?

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

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

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

Which MCP server has more tools and community activity?

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

Can I use both Devilge and Google Surf Mcp 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 Devilge or Google Surf Mcp 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 Devilge and Google Surf Mcp free to use, or do they require API keys?

Devilge is listed under a Free / Open Source model with No auth required . Google Surf Mcp 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 Devilge and Google Surf Mcp at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both devilge and google-surf-mcp 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, Devilge has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Google Surf Mcp holds a Quality Score of 61 /100 ( Good ) with 0 views, 0 installs, and 277 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Devilge vs Google Surf Mcp

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

Devilge

Browser Automation · Local stdio

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

Google Surf Mcp

Browser Automation · Local stdio

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

Verdict Summary: Choose Devilge if you need specialized Browser Automation tools running via a local process. Choose Google Surf Mcp 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 Devilge 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 Devilge Details

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

Feature & Specification Comparison

Specification	D Devilge Browser Automation	G Google Surf Mcp Browser Automation
Summary	Android/KMM MCP server: logcat, ADB device control, Compose previews, network, Maestro flows.	Google search via Playwright with a warm Chrome profile. No API key, no proxies.
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Devilge Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Google Surf Mcp Tools (20)

dropped

dropped_reasons

liteparse

content

title

excerpt

length

is_pdf

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

Devilge Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "devilge": {
      "command": "npx",
      "args": [
        "-y",
        "devilge"
      ]
    }
  }
}

Google Surf Mcp Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Devilge More alternatives to Google Surf Mcp Browser Automation category hub