Skip to content
Kitbay
Submit

Chrome DevTools MCP servers and agent skills

93 MCP servers and 60 agent skills connect AI assistants to Chrome DevTools. Includes Google's official listings.

Web developer tools built into Google Chrome for inspecting, debugging and profiling pages.

93 MCP servers60 skills9 officialGoogle

Last checked

All listings

153

Sorted: official first, then quality and activity.Show all, including less active listings

How AI connects to Chrome DevTools

Chrome's debugging features are available to programs through the Chrome DevTools Protocol, documented in a protocol viewer for the latest and stable Chrome versions and for the V8 inspector used by Node.js; TypeScript definitions ship as the devtools-protocol npm package. The ChromeDevTools team also publishes chrome-devtools-mcp, an MCP server and CLI that lets coding agents control a live Chrome: recording performance traces, inspecting network requests and console messages, taking screenshots and automating pages through Puppeteer.

From the vendor's documentation: ChromeDevTools/devtools-protocol on GitHub, ChromeDevTools/chrome-devtools-mcp on GitHub

Guides:MCP servers vs agent skillsConnecting MCP servers to AI clients

Questions

Is there an official Chrome DevTools MCP server?
Yes. 9 listings for Chrome DevTools are published by the tool's vendor, marked Official in the table above with a link to the evidence.
Can Claude use Chrome DevTools?
Yes, through an MCP server. 93 MCP servers connect Claude and other AI assistants to Chrome DevTools; each listing shows how it connects and how to install it.
Are there agent skills for Chrome DevTools?
Yes: 60 skills are listed. Skills are folders of instructions (and sometimes scripts) that an agent loads when a task needs them.
Which AI clients do Chrome DevTools servers and skills support?
The listings on this page most often document claude-code, vscode, gemini-cli, codex. Each listing shows the clients its own documentation names.