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.
Continue.dev is one of the few MCP clients configured in YAML, so most copy-paste JSON snippets from server READMEs won't work as-is. This page gives you the translated config for Chrome DevTools MCP — the Chrome team's official server (43.2k GitHub stars) for inspecting, debugging, and profiling live web pages.
Connected to Continue's agent mode, it turns 'why is this page broken' into something your editor assistant can answer by actually loading the page, instead of pattern-matching on your source code.
Where Continue.dev keeps MCP config
You have two options. Global: add an mcpServers block to ~/.continue/config.yaml, and the server is available in every workspace. Per-project: drop a standalone YAML file into .continue/mcpServers/ inside the repo — handy for committing browser-debugging capability alongside a frontend project so collaborators inherit it.
Either way the server definition is the same: a name, a command, and args. Continue spawns the process over stdio when the agent needs it.
The YAML block
Add this to ~/.continue/config.yaml (or save it as .continue/mcpServers/chrome-devtools.yaml in a project, keeping the same mcpServers key). Note that args is a YAML list — each argument on its own line:
mcpServers:
- name: chrome-devtools
command: npx
args:
- chrome-devtools-mcp@latestReload and run a first task
Reload the Continue extension (or restart your editor) so it re-reads the config. MCP tools surface in Continue's agent mode, so switch to it and try: 'open my dev server at localhost:3000 and report console errors and failed network requests.' The first invocation is slow while npx pulls the package and Chrome starts; later calls reuse the running browser.
Chrome DevTools MCP's live listing — including its current tool list — is on the Loomal marketplace at https://loomal.ai/marketplace/chrome-devtools-mcp.
Troubleshooting in Continue.dev
YAML indentation is the top failure mode. The dash before name must be indented under mcpServers, and command/args must align with name — a tab character or one missing space and Continue silently drops the block. If the server never appears, run your config through a YAML validator before anything else.
If the config parses but tools don't show, check three things: you're in agent mode (MCP tools don't apply to plain autocomplete), the extension was actually reloaded after the edit, and `npx chrome-devtools-mcp@latest` runs cleanly in a terminal. For project-scoped files, confirm the file extension is .yaml and it sits in .continue/mcpServers/, not .continue/ directly. Chrome must also be installed on the machine — the server launches it rather than bundling a browser.
FAQ
How do I install Chrome DevTools MCP in Continue.dev?
Add an mcpServers block to ~/.continue/config.yaml with command npx and the chrome-devtools-mcp@latest argument, or drop the same YAML into .continue/mcpServers/ in your project. Reload the Continue extension and the tools appear in agent mode.
Continue.dev uses YAML? Most MCP docs show JSON.
Yes — Continue moved its configuration to config.yaml. When a server README gives you a JSON mcpServers snippet, translate it: the JSON object key becomes the name field, and the command and args carry over as YAML scalars and a list.
Why don't the browser tools show up in my chat?
MCP tools are an agent-mode feature in Continue. If you're in regular chat or autocomplete, they won't be offered. Switch modes, and if they're still missing, reload the extension and validate your YAML indentation.
Can I share this setup with my team?
Yes — commit a YAML file under .continue/mcpServers/ in the repo. Anyone using Continue.dev in that project picks up the Chrome DevTools server automatically, provided they have Node and Chrome installed locally.
More MCP servers for Continue.dev.
Explore the Loomal marketplace, with live tool lists on every server page.