Chrome Debugger MCP vs Xdebug

In-depth architectural comparison of the Chrome Debugger MCP and Xdebug 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 Chrome Debugger 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 Chrome Debugger MCP Details

Choose Xdebug 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 Xdebug Details

Feature & Specification Comparison

Specification	Chrome Debugger MCP Developer Tools	Xdebug Developer Tools
Summary	Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code	MCP server for PHP Xdebug debugging with breakpoints, stepping, and variable inspection
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": {
    "chrome-debugger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-debugger-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons