Chrome DevTools MCP
by DevTarlow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | `launch` starts a fresh Chrome for each chat. Use `attach` to drive a browser you started yourself. | launch |
| endpoint | No | Required by `attach`: the debugging address of the browser you started, such as `http://127.0.0.1:9222`. | |
| headless | No | `false` opens a window you can watch. Set `true` on a server or in CI, where there is no display. | false |
| executablePath | No | Which Chrome to launch. Left unset, the plugin finds it. Set it for an unusual install, or for the wrapper that adds `--no-sandbox`. | |
| toolCallTimeoutMs | No | How long one tool call may take, in milliseconds. Defaults to the client's own value. | |
| CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS | No | Set to `1` to silence the `Update available: 1.9.0 -> 1.10.1` notice printed by the Chrome DevTools MCP server. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues