mcpbeat

Browser Devtools MCP Server

io.github.serkan-ozal/browser-devtools-mcp
not responding

Browser Devtools MCP is listed as active in the registry but did not answer our last check. 5 200 installs a week from npm.

Playwright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 817 · avg 729 · -3% w/w
a month agotoday
Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 92 checks
—
Tools
hidden behind auth
2 ms
Response time
average over 24h
5 200
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add browser-devtools-mcp --transport http https://{your_mcp_server_host}/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "browser-devtools-mcp": {
      "url": "https://{your_mcp_server_host}/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.browser-devtools-mcp]
url = "https://{your_mcp_server_host}/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "browser-devtools-mcp": {
      "url": "https://{your_mcp_server_host}/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "browser-devtools-mcp": {
      "url": "https://{your_mcp_server_host}/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://{your_mcp_server_host}/mcp streamable-http answering 2 ms 0 min ago

Browser Devtools MCP — questions

Answers built from our own checks of this server.

Is Browser Devtools MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 2 ms. The bar chart above shows every period we have measured.
Is Browser Devtools MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Browser Devtools MCP as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Browser Devtools MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Browser Devtools MCP need an API key?
No. Browser Devtools MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How many people use Browser Devtools MCP?
The npm package browser-devtools-mcp was installed 5 200 times in the last week. Week over week that is -3%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.