Browser Tools MCP — Casos de uso, Instalar & Demo ao vivo

Name: Browser Tools MCP Server
Author: AgentDeskAI

Por que usar

Principais recursos

Reads YOUR Chrome, not a headless one — logged-in auth, extensions, cookies
Console logs, network requests, selected-element inspection
Built-in audits: Lighthouse-style perf, a11y, SEO, Best Practices, Next.js
All data stays local — no cloud roundtrip

Demo ao vivo

Como fica na prática

browser-tools.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.cursor/mcp.json · .cursor/mcp.json

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: Browser Tools

Debug a live front-end bug using real console + network context

👤 Frontend engineers ⏱ ~15 min intermediate

Quando usar: A bug only reproduces in your actual session (logged in, specific data). You want the agent to read the console and network tab.

Pré-requisitos

Chrome extension installed + bridge server running — Install extension from releases page, then npx @agentdeskai/browser-tools-server@latest in a terminal
MCP server wired to your client — npx -y @agentdeskai/browser-tools-mcp@latest

Fluxo

Reproduce the bug with DevTools open

Open the affected page in Chrome with the extension active. Trigger the bug. Don't close the tab.✓ Copiado

→ Bug visible, extension icon shows it's capturing
Pull context into the agent

Get the last 50 console messages and any failed network requests. Summarize what the page is yelling about.✓ Copiado

→ Specific errors surfaced with stack traces
Diagnose and propose fix

Based on the errors, point at the file/line likely responsible. If 404s, identify the bad URL; if JS errors, the root cause.✓ Copiado

→ Concrete hypothesis with evidence

Resultado: A debugging loop where the agent has the same context as you opening DevTools — faster than reading a screenshot description.

Armadilhas

Bridge server not running, MCP silently returns empty data — Always check curl localhost:3025/identity responds first; the bridge must be running before the MCP call
Capturing from the wrong tab — Extension captures the active tab. Click into the right tab before asking the agent

Combine com: sentry

Run a Lighthouse-style audit on the page you're looking at

👤 Frontend / SEO / a11y engineers ⏱ ~10 min beginner

Quando usar: You want to audit a page as it actually renders in your session (not a clean crawler).

Fluxo

Open the target page

Navigate to <URL> in Chrome with the extension active.✓ Copiado

→ Page loaded
Run the audit mode

Run the audit tool — perf, a11y, SEO, best practices. Summarize top 5 issues with fix suggestions.✓ Copiado

→ Prioritized issue list
Focus in

For the accessibility failures, list exact selectors and the WCAG rule violated.✓ Copiado

→ Actionable remediation steps

Resultado: A full audit without leaving your browser, scoped to real user state.

Armadilhas

Audits for auth-gated pages fail because the tool re-navigates — Use the debugger mode's element/console tools on the already-loaded page instead of the full audit

Inspect and explain a specific element

👤 Frontend devs, designers ⏱ ~5 min beginner

Quando usar: Something looks off in one component. You want a quick 'what CSS is applied and why' without digging.

Fluxo

Select the element in DevTools

Open DevTools, click the element inspector, select the offending element.✓ Copiado

→ Element highlighted in Elements panel
Ask the agent to inspect

Get the selected element's computed styles, inherited rules, and bounding box. Explain why it's rendering the way it is.✓ Copiado

→ Explanation grounded in actual CSS cascade
Propose a fix

Suggest the smallest CSS change to achieve [desired visual]. Show the before/after rule.✓ Copiado

→ Minimal diff suggestion

Resultado: CSS debugging at conversation speed.

Armadilhas

Element selection doesn't persist — agent sees a different one — Re-select the element right before asking; don't let the DevTools panel change focus between messages

Combinações

Combine com outros MCPs para 10× de alavancagem

browser-tools + sentry

Reproduce a Sentry error in YOUR browser and pull live console context

Sentry issue WEB-3a91 says an XHR to /api/checkout returns 500. Navigate to the page in my Chrome, reproduce, and capture the console + network.✓ Copiado

browser-tools + playwright

browser-tools for live debugging, Playwright for repeatable reproductions afterward

I found the bug in my live Chrome via browser-tools. Now write a Playwright test that reproduces the exact click sequence.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Quando chamar	Custo
takeScreenshot	Visual capture of current state	free
getConsoleLogs / getConsoleErrors	Debug any JS error	free
getNetworkLogs / getNetworkErrors	Diagnose failed API calls	free
getSelectedElement	User has selected an element in DevTools	free
runAccessibilityAudit	A11y review of current page	free
runPerformanceAudit	Perf audit of current page	free
runSEOAudit	SEO review	free
runBestPracticesAudit	General code quality review	free
runNextJSAudit	You're on Next.js	free
wipeLogs	Clear between investigation sessions	free

Custo e limites

O que custa rodar

Cota de API: None — all local
Tokens por chamada: Log dumps can be big (5k+ tokens). Use wipeLogs between sessions.
Monetário: Free, open source
Dica: Wipe logs before each investigation — avoids pulling in unrelated noise

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None — runs against your existing Chrome session

Saída de dados: Only to localhost:3025 (the bridge). Nothing leaves your machine except via whatever the agent/MCP client does.

Extension has access to your browser data by design. Only install from official releases. Review source before granting permissions.

Solução de problemas

Erros comuns e correções

All tools return empty / 'not connected'

The bridge server isn't running. Start it: npx @agentdeskai/browser-tools-server@latest in a dedicated terminal.

Verificar: curl http://localhost:3025/identity

Extension icon grey / inactive

Click the extension icon, confirm it says 'Connected'. If not, reload the tab.

Audits fail with timeout

Some audits need extra time on heavy pages. Close other tabs to free CPU; re-run.

Wrong tab captured

The extension captures the tab that was last activated. Click into the right tab immediately before calling a tool.

Alternativas

Browser Tools vs. outros

Alternativa	Quando usar	Troca
chrome-devtools MCP	You want direct CDP access without a browser extension	No extension needed but you lose real-user-session context
Playwright MCP	You need repeatable automation, not live debugging	Clean browser — can't see your logged-in session

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills