Chrome ToolsSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP server that provides tools for interacting with Chrome through its DevTools Protocol. This server enables remote control of Chrome tabs, including executing JavaScript, capturing screenshots, monitoring network traffic, and more.
Why use an MCP server like this?
This type of MCP Server is useful When you need to manually configure your browser to be in a certain state before you let an AI tool like Cline poke at it. You can also use this tool to listen to and pull network events into its context.
Features
- List Chrome tabs
- Execute JavaScript in tabs
- Capture screenshots
- Monitor network traffic
- Navigate tabs to URLs
- Query DOM elements
- Click elements with console output capture
Installation
npm install @nicholmikey/chrome-tools
Configuration
The server can be configured through environment variables in your MCP settings:
{
"chrome-tools": {
"command": "node",
"args": ["path/to/chrome-tools/dist/index.js"],
"env": {
"CHROME_DEBUG_URL": "http://localhost:9222",
"CHROME_CONNECTION_TYPE": "direct",
"CHROME_ERROR_HELP": "custom error message"
}
}
}Environment Variables
CHROME_DEBUG_URL: The URL where Chrome's remote debugging interface is available (default: http://localhost:9222)CHROME_CONNECTION_TYPE: Connection type identifier for logging (e.g., "direct", "ssh-tunnel", "docker")CHROME_ERROR_HELP: Custom error message shown when connection fails
Setup Guide
Native Setup (Windows/Mac/Linux)
- Launch Chrome with remote debugging enabled:
# Windows "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 # Mac /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 # Linux google-chrome --remote-debugging-port=9222
- Configure MCP settings:
{
"env": {
"CHROME_DEBUG_URL": "http://localhost2a6aa6ca363cOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add chrome-tools -- npx -y @nicholmikey/[email protected]
{
"mcpServers": {
"chrome-tools": {
"command": "npx",
"args": [
"-y",
"@nicholmikey/[email protected]"
]
}
}
}Exposed tools (7)
6 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
capture_network_events | read | |
capture_screenshot | read | |
click_element | read | |
execute_script | write | |
list_tabs | read | |
load_url | read | |
query_dom_elements | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@modelcontextprotocol/sdk, @types/ws, axios, chrome-remote-interface, sharp, ts-node, typescript, ws
Gates applied: no_behavioural_pass.
2a6aa6ca363cfull audit observations/trust-audit/mcp-server/nicholmikey__chrome-tools.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 2a6aa6ca363c | SAFE | B | 89 | first audit |
Questions
What tools does Chrome Tools expose?
7 in total: 6 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Chrome Tools safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Chrome Tools need?
No credential environment variables were found in its source, so it appears to need none.
How does Chrome Tools run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @nicholmikey/chrome-tools at 1.3.0.
How current is this page?
The grade is for one exact copy of the source (2a6aa6ca363c), read on 2026-10-08. The repository is watched and re-audited when it changes.