BrowserTools MCP

listing.by

Read live console logs, network requests, screenshots and Lighthouse audits from your own Chrome session.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

npx -y @agentdeskai/browser-tools-mcp@latest

listing.local.needs listing.local.note

  • BROWSER_TOOLS_PORT listing.env.optional Port the connector listens on for the browser extension. Defaults to 3025.
  • BROWSER_TOOLS_SCREENSHOT_DIR listing.env.optional Directory screenshots are written to. Defaults to ~/Downloads/mcp-screenshots.
  • BROWSER_TOOLS_TOOLS listing.env.optional Comma-separated allowlist of tools to expose. All tools are exposed by default.
act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/browser-tools

listing.about

BrowserTools exposes live telemetry from your real Chrome session to an MCP-compatible assistant or IDE such as Cursor. It provides console output, network requests, screenshots and Lighthouse audits, so the assistant can debug a page you already have open.

It runs locally over stdio with npx and embeds the browser connector, so no separate server process is needed. It pairs with a Chrome extension from the repository, loaded unpacked. No sign-in or API key is required. Node 22.19 or newer is needed.

listing.can

  • Read console output from your live Chrome session
  • Inspect network requests made by the page
  • Capture screenshots saved to a local directory
  • Run Lighthouse audits on the current page
  • Limit exposed tools with an allowlist environment variable

listing.tools

listing.notools.local

listing.prompts

  • Check the browser console for errors on the page I have open.

  • Show the failed network requests from my current tab.

  • Take a screenshot of the page and describe layout problems.

  • Run a Lighthouse audit on this page and summarize the issues.

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio browser-tools -- npx -y @agentdeskai/browser-tools-mcp@latest
  1. Start Claude Code and type /mcp. browser-tools should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@agentdeskai/browser-tools-mcp@latest"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@agentdeskai/browser-tools-mcp@latest"
      ]
    }
  }
}

Needs Node.js on your computer.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"browser-tools","type":"stdio","command":"npx","args":["-y","@agentdeskai/browser-tools-mcp@latest"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "browser-tools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@agentdeskai/browser-tools-mcp@latest"
      ]
    }
  }
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@agentdeskai/browser-tools-mcp@latest"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add browser-tools -- npx -y @agentdeskai/browser-tools-mcp@latest

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.browser-tools]
command = "npx"
args = ["-y", "@agentdeskai/browser-tools-mcp@latest"]

Needs Node.js on your computer.

Gemini CLI

gemini mcp add browser-tools npx -- -y @agentdeskai/browser-tools-mcp@latest

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@agentdeskai/browser-tools-mcp@latest"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

listing.faq

Can I paste mcp.tc/i/browser-tools into my MCP client?

No. BrowserTools MCP runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @agentdeskai/browser-tools-mcp@latest.

Does BrowserTools MCP need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is BrowserTools MCP a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @agentdeskai/browser-tools-mcp@latest, which needs Node.js.

What can BrowserTools MCP do?

You can read console output from your live Chrome session, inspect network requests made by the page and capture screenshots saved to a local directory.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read BrowserTools MCP's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![BrowserTools MCP on mcp.tc](https://mcp.tc/i/browser-tools/badge.svg)](https://mcp.tc/i/browser-tools)
HTML
<a href="https://mcp.tc/i/browser-tools"><img src="https://mcp.tc/i/browser-tools/badge.svg" alt="BrowserTools MCP on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/browser-tools.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/browser-tools" title="BrowserTools MCP on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/browser-tools.json

listing.em.fields

listing.related

listing.more_in

  • Browser Use

    Browser Automation

    state.local.label (state.local.title)

    Drive a real Chrome browser with an AI agent to navigate sites, fill forms and extract data.

    mcp.tc/i/browser-use

  • Chrome DevTools MCPvf.sr

    Google (Chrome DevTools)

    state.local.label (state.local.title)

    Control and inspect a live Chrome browser: record performance traces, analyze network requests, and read console messages.

    mcp.tc/i/chrome-devtools

  • Playwright MCPvf.sr

    Microsoft

    state.local.label (state.local.title)

    Automate a real browser through Playwright accessibility snapshots instead of screenshots.

    mcp.tc/i/playwright

  • Agent Infra Browser

    ByteDance

    state.local.label (state.local.title)

    Give an assistant control of a browser through a local MCP server from the Agent TARS and UI-TARS project.

    mcp.tc/i/agent-infra-browser

  • Kernel

    Browser Automation

    state.auth.label (state.auth.title)

    Launch and control cloud Chromium browsers, run Playwright code, and manage Kernel apps and deployments from your assistant.

    mcp.tc/i/kernel

  • Browser Use Cloud

    Browser Use

    state.key.label (state.key.title)

    Run cloud browser-agent sessions for web tasks, form filling and data extraction, with follow-up tasks and saved login profiles.

    mcp.tc/i/browser-use-cloud

listing.disclaimer_checked