Chrome MCP Server

If you already use Chrome, the chrome mcp server is the piece that lets your assistant work with it directly. Your real, logged-in Chrome as an MCP server: 60 token-efficient web-dev tools. ChromeOS included.

What the server does

63 web-development tools (navigation, DOM inspection, visual regression, audits, network mocking) over a local WebSocket bridge, plus a headless instance for CI. Self-hosted, local-only.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Group — N
• Interaction — 11
• Audits — 6

Credentials and setup notes

Configuration is passed through the environment: CHROME_BRIDGE_HOST, CHROME_BRIDGE_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chrome's toolset — Group, Interaction, Audits — is a fair guide to whether it matches your workflow. It is maintained by frsorrentino; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Chrome's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.