Browser Agent vs DrissionPage MCP

In-depth architectural comparison of the Browser Agent and DrissionPage 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.

Which MCP Server Should You Choose?

B

Choose Browser Agent when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: browser-agent.

Explore Browser Agent Details

Choose DrissionPage MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore DrissionPage MCP Details

Feature & Specification Comparison

Specification	B Browser Agent Developer Tools	DrissionPage MCP Developer Tools
Summary	MCP server for browser automation with AI agent	Local browser automation for MCP clients powered by DrissionPage.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "browser-agent": {
      "command": "npx",
      "args": [
        "-y",
        "runbook-ai-mcp@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "drissionpage-mcp": {
      "command": "uvx",
      "args": [
        "drissionpage-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons