MCP Browser Kit vs MCP Server Browser

In-depth architectural comparison of the MCP Browser Kit and MCP Server Browser 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?

Choose MCP Browser Kit 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: Supports Chromium-based, Firefox, Brave, Edge, and Safari browsers, Two extension builds (M2 with more features, M3 with broader compatibility), Local stdio or HTTP transport for MCP communication.

Explore MCP Browser Kit Details

Choose MCP Server Browser 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: Puppeteer-based browser automation, Local browser connections, Remote browser connections.

Feature & Specification Comparison

Specification	MCP Browser Kit ndthanhdev Browser Automation	MCP Server Browser agent-infra Browser Automation
Summary
Category & Scope	Browser Automation	Browser Automation

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": {
    "ndthanhdev-mcp-browser-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-browser-kit/server@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "agent-infra-mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-tars/cli@latest"
      ]
    }
  }
}

Related MCP Server Comparisons