Connect any MCP server to your client.
Config-file-accurate install steps for every major MCP client.
Chrome DevTools MCP server in Claude Code.
Give Claude Code a real browser to debug against. One CLI command registers the official Chrome DevTools MCP server, and your agent can inspect, profile, and screenshot live pages without leaving the terminal.
Chrome DevTools MCP server in Claude Desktop.
Let Claude Desktop open a real Chrome window, read console errors, and profile page performance. One JSON entry in claude_desktop_config.json and a full restart is all it takes.
Chrome DevTools MCP server in Cline.
Cline writes your frontend code inside VS Code — Chrome DevTools MCP lets it check the result in a real browser. Here's the cline_mcp_settings.json entry and where that file actually hides.
Chrome DevTools MCP server in Continue.dev.
Continue.dev configures MCP servers in YAML, not JSON. Here's the exact block for Chrome DevTools MCP — globally in config.yaml or per-project in .continue/mcpServers/ — and the indentation traps to avoid.
Chrome DevTools MCP server in Cursor.
Cursor's agent can already write your frontend — with Chrome DevTools MCP it can also load the page, read the console, and profile what it built. Setup is one mcp.json entry and a toggle.
Chrome DevTools MCP server in LangChain.
No config file here — LangChain connects to MCP servers in code. Use langchain-mcp-adapters to spawn Chrome DevTools MCP over stdio and hand its browser tools to any agent you build.
Chrome DevTools MCP server in n8n.
n8n's MCP Client Tool node speaks HTTP, while Chrome DevTools MCP speaks stdio. The fix is a small gateway process — here's the bridge command and the node settings to point at it.
Chrome DevTools MCP server in VS Code (GitHub Copilot).
Copilot's agent mode supports MCP natively in VS Code — but the config key is "servers", not "mcpServers", and that one detail breaks most copy-pasted setups. Here's the correct config.
Chrome DevTools MCP server in Windsurf.
Give Cascade a live Chrome to verify its frontend work in. Windsurf keeps all MCP config in one global file — ~/.codeium/windsurf/mcp_config.json — and here's exactly what goes in it.
Chrome DevTools MCP server in Zed.
Zed calls them context servers, and they live in your main settings.json under a context_servers key. Here's the entry that gets Chrome DevTools MCP running in Zed's Agent Panel.