BrowserTools MCP

MCP server by AgentDesk AI

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

Runs locally (Runs on your machine: its page has the install command)Runs with npx

Install BrowserTools MCP

Runs on your machine. Your client starts it with this command:

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

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

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

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/browser-tools

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.

What you can do

  • 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

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example 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.

Set up

Every client starts BrowserTools MCP on your machine with the same command. Pick yours; the page remembers your choice.

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

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

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.

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.

Embed

Show BrowserTools MCP in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, 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>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

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

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

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>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

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

What each field means

mcp.tc isn’t affiliated with AgentDesk AI. This page was built from BrowserTools MCP’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.