Chrome DevTools

Commands and config follow each client’s own MCP docs. Some servers also need an API key or environment variables; see the server’s documentation.

claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp

codex mcp add chrome-devtools -- npx -y chrome-devtools-mcp

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

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

{
  "servers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.

• Claude Code Transport supported
• Codex Transport supported
• Cursor Transport supported
• Gemini CLI Transport supported
• VS Code Client docs don’t list transports
• ChatGPT No shared transport
• Claude Client docs don’t list transports
• Cline Transport supported
• Devin Desktop Transport supported
• GitHub Copilot Client docs don’t list transports
• JetBrains AI Assistant Transport supported
• Kiro Transport supported
• OpenCode Client docs don’t list transports
• Zed Client docs don’t list transports

• Official MCP Registry registry.modelcontextprotocol.io · checked Sep 28, 2026
• Chrome DevTools: vendor documentation developer.chrome.com · checked Oct 5, 2026

This data comes from the Official MCP Registry.