Drive a browser

Chrome DevTools MCP

Open-source MCP server and CLI that lets an agent control, inspect and profile a local Chrome browser.

At a glance

Provider: Google Chrome DevTools team
Category: Drive a browser
Type: Runs on your machine
Pricing model: Free, open source7
Free tier: Free; no paid plan7
Authentication: None; runs locally1
Connect via: Local MCP server (stdio via npx), chrome-devtools CLI1
Read from the provider's pages: 2026-11-04

Pricing

Pricing model: Free, open source under Apache-2.0
Free tier: Whole tool is free
Card required for free tier: No; nothing to sign up for

Pricing in full →Tools

Official MCP server: Yes, local
Address or package: chrome-devtools-mcp on npm, run with npx -y chrome-devtools-mcp@latest

Tools in full →Authentication

Who creates the account: No account
Where to get a key: No key needed
Other requirements: Node.js LTS, current stable Chrome and npm

Authentication in full →Setup

REST API: Not published
MCP server: Local stdio process started by the client with npx
OpenAPI spec: Not published

Setup in full →Limits

Rate limit: Not published

Limits in full →Privacy

Data location: Runs on the user's machine; page content goes to the connected MCP client
Retention: Default profile kept on disk until removed; --isolated clears it when the browser closes
Used for training: Not published

Privacy in full →

Read from Google Chrome DevTools team’s own pages on 2026-11-04. Every number links to the page a value came from. For agents, the same facts as markdown: /tools/drive-a-browser/chrome-devtools-mcp.md