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.
GitHub Copilot's agent mode in VS Code can use MCP tools, which means it can do more than reason about your frontend source — with Chrome DevTools MCP attached, it can load the running app, read the console, and trace performance. The server is the Chrome DevTools team's own project, with 43.2k stars on GitHub.
VS Code's MCP support has its own configuration schema that differs slightly from other clients, plus an explicit start step and a trust prompt. This guide walks the exact sequence.
Two ways in: Command Palette or mcp.json
The guided route: open the Command Palette and run MCP: Add Server, choose the npm/stdio option, and enter `npx chrome-devtools-mcp@latest`. VS Code asks whether to store it in your user settings (available everywhere) or the workspace (committed with the repo).
The direct route: create .vscode/mcp.json in your project. This is the file VS Code reads for workspace-scoped MCP servers, and it's the right choice when you want the config in version control next to the frontend it debugs.
The .vscode/mcp.json entry
Note the top-level key — VS Code uses "servers", unlike the "mcpServers" key used by Claude Desktop, Cursor, and most README snippets. Pasting an mcpServers block here fails silently:
{
"servers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
}
}
}Start the server and switch to agent mode
Saving the file isn't the end: VS Code shows a Start action above the server entry in mcp.json (and in the MCP view of the Extensions area). Click it, accept the trust prompt for the new server, and watch the status change to running with a tool count.
Then open Copilot Chat, switch the mode picker to Agent, and check the tools icon — the chrome-devtools tools should be listed and toggleable. Ask Copilot to open your dev server and report console errors to confirm the loop works end to end. The server's live tool list is on its Loomal listing at https://loomal.ai/marketplace/chrome-devtools-mcp.
Troubleshooting in VS Code
If the server never appears, re-check the schema first: "servers" as the top-level key, in .vscode/mcp.json — not settings.json, and not an mcpServers block. Workspace files also require the folder to be trusted; restricted-mode workspaces won't start MCP servers.
If it appears but won't start, open the server's output channel (the MCP view links to it) to read stderr. The common failures are Node not installed, npx not on PATH for the VS Code process, or Chrome missing from the machine. Verify with `npx chrome-devtools-mcp@latest` in the integrated terminal. Finally, remember tools only fire in agent mode — in ask mode, Copilot will happily discuss your bug without ever opening the browser.
FAQ
How do I install Chrome DevTools MCP in VS Code with Copilot?
Run MCP: Add Server from the Command Palette and enter `npx chrome-devtools-mcp@latest`, or create .vscode/mcp.json with a "servers" entry. Then click Start on the server and use Copilot Chat in agent mode.
Why doesn't my pasted config from the server README work?
Most READMEs show the "mcpServers" key used by Claude Desktop and Cursor. VS Code's mcp.json uses "servers" instead. Rename the key, keep the command and args, and reload.
The server is configured but Copilot never uses the browser tools.
Three checks: the server is started (Start action in the MCP view), you're in agent mode rather than ask mode, and the tools are enabled in the tools picker for the chat. Any one of those being off keeps the tools invisible to Copilot.
Can I share this setup through the repo?
Yes — commit .vscode/mcp.json. Teammates opening the workspace get prompted to trust and start the server. They'll need Node and Chrome locally, since the server runs on each developer's machine.
More MCP servers for VS Code.
Browse the Loomal marketplace — tool lists are probed live on every listing.