Other · Remote MCP server

Browser Devtools MCP

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

Visit Browser Devtools MCP's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.serkan-ozal/browser-devtools-mcp
Version
0.9.1
Status
Active
Category
other
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-05-12
Updated
2026-05-12
Publisher
serkan-ozal (GitHub)
Website
github.com/serkan-ozal/browser-devtools-mcp
Repository
github.com/serkan-ozal/browser-devtools-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://{your_mcp_server_host}/mcpNone

Packages

RegistryPackageVersionTransportEnvironment variables
npmbrowser-devtools-mcp0.9.1stdioPLATFORM, PORT, SESSION_IDLE_SECONDS, SESSION_IDLE_CHECK_SECONDS, SESSION_CLOSE_ON_SOCKET_CLOSE, CONSOLE_MESSAGES_BUFFER_SIZE, HTTP_REQUESTS_BUFFER_SIZE, BROWSER_SERVER_INSTRUCTIONS_ENABLE, BROWSER_POLICY_UI_DEBUGGING_ENABLE, BROWSER_HEADLESS_ENABLE, BROWSER_PERSISTENT_ENABLE, BROWSER_CDP_ENDPOINT_URL, BROWSER_CDP_ENABLE, BROWSER_CDP_OPEN_INSPECT, BROWSER_PERSISTENT_USER_DATA_DIR, BROWSER_USE_INSTALLED_ON_SYSTEM, BROWSER_EXECUTABLE_PATH, BROWSER_CHROMIUM_SANDBOX, BROWSER_LAUNCH_ARGS, BROWSER_ALLOWED_DOMAINS

How to connect Browser Devtools MCP

Browser Devtools MCP is a remote MCP server: there is nothing to install. Its endpoint is https://{your_mcp_server_host}/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The URL contains placeholders to fill in before connecting: {your_mcp_server_host}.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: browser-devtools-mcp version 0.9.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y browser-devtools-mcp@0.9.1. It reads these environment variables: PLATFORM, PORT, SESSION_IDLE_SECONDS, SESSION_IDLE_CHECK_SECONDS, SESSION_CLOSE_ON_SOCKET_CLOSE, CONSOLE_MESSAGES_BUFFER_SIZE, HTTP_REQUESTS_BUFFER_SIZE, BROWSER_SERVER_INSTRUCTIONS_ENABLE, BROWSER_POLICY_UI_DEBUGGING_ENABLE, BROWSER_HEADLESS_ENABLE, BROWSER_PERSISTENT_ENABLE, BROWSER_CDP_ENDPOINT_URL, BROWSER_CDP_ENABLE, BROWSER_CDP_OPEN_INSPECT, BROWSER_PERSISTENT_USER_DATA_DIR, BROWSER_USE_INSTALLED_ON_SYSTEM, BROWSER_EXECUTABLE_PATH, BROWSER_CHROMIUM_SANDBOX, BROWSER_LAUNCH_ARGS and BROWSER_ALLOWED_DOMAINS; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "browser-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "browser-devtools-mcp@0.9.1"
      ],
      "env": {
        "PLATFORM": "<value>",
        "PORT": "<value>",
        "SESSION_IDLE_SECONDS": "<value>",
        "SESSION_IDLE_CHECK_SECONDS": "<value>",
        "SESSION_CLOSE_ON_SOCKET_CLOSE": "<value>",
        "CONSOLE_MESSAGES_BUFFER_SIZE": "<value>",
        "HTTP_REQUESTS_BUFFER_SIZE": "<value>",
        "BROWSER_SERVER_INSTRUCTIONS_ENABLE": "<value>",
        "BROWSER_POLICY_UI_DEBUGGING_ENABLE": "<value>",
        "BROWSER_HEADLESS_ENABLE": "<value>",
        "BROWSER_PERSISTENT_ENABLE": "<value>",
        "BROWSER_CDP_ENDPOINT_URL": "<value>",
        "BROWSER_CDP_ENABLE": "<value>",
        "BROWSER_CDP_OPEN_INSPECT": "<value>",
        "BROWSER_PERSISTENT_USER_DATA_DIR": "<value>",
        "BROWSER_USE_INSTALLED_ON_SYSTEM": "<value>",
        "BROWSER_EXECUTABLE_PATH": "<value>",
        "BROWSER_CHROMIUM_SANDBOX": "<value>",
        "BROWSER_LAUNCH_ARGS": "<value>",
        "BROWSER_ALLOWED_DOMAINS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 6,730 →
ServerRunsEndpoint or package
Brixa StudioYour design, automated endlessly. Design anywhere, Brixa freezes it as a template, publishes forever.Remote · HTTPmcp.brixastudio.com
brokreAI-safe credential broker for MCP — run saved SSH/MySQL/psql aliases; passwords never reach AI.Local · stdionpm: brokre
BrowsegrabToken-efficient browser agent for local LLMs. Playwright + accessibility tree + MarkGrab.Local · stdioPyPI: browsegrab
BrowsenticHands your real, logged-in browser to your agent: an AI side panel extension, also over MCP.Local · stdionpm: browsentic
Browser GatewayAI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.Local · stdionpm: browser-gateway
Browser MCPControl a local headless Chrome browser: open pages, read titles, and take screenshots.Local · stdionpm: @mrfentmen/browser-mcp
Browser MCPHosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.Remote · HTTPbrowser.regiq.in
Browser MCP CdpLocal Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support.Local · stdionpm: browser-mcp-cdp