Browser Automation MCP Servers

8 browser automation MCP servers are cataloged, 0 with verified current-spec support.

MCP servers that drive or inspect web browsers: page navigation, form filling, DOM and accessibility inspection, debugging, and end-to-end testing.

• Browser Use MCP Server - Earlier Revision

  MCP server shipped inside the browser-use Python library for driving a real Chrome browser, run locally over stdio. The registry-published package launches the minimal --cli-mcp variant (browser_exec, browser_screenshot); the richer tool set documented on docs.browser-use.com runs behind the --mcp flag. No vendor documentation surface names a supported MCP revision. Resolved from the published package: browser-use 0.13.8 depends on mcp@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• browser-devtools-mcp - Earlier Revision

  Distributed as npm:browser-devtools-mcp. Resolved from the published package: browser-devtools-mcp 0.9.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• BrowserStack MCP Server - Earlier Revision

  BrowserStack's official MCP server for its testing platform, run locally from the @browserstack/mcp-server npm package with BrowserStack account credentials. No vendor documentation surface names a supported MCP revision. npm's latest (1.2.36, 2026-08-11) is well ahead of the registry record (1.0.0, 2025-10-28). Resolved from the published package: @browserstack/mcp-server 1.2.36 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Chrome DevTools MCP - Spec Support Unverified

  Google's Chrome DevTools MCP server: lets a coding agent control and inspect a live Chrome browser with DevTools-grade debugging, performance tracing, and Puppeteer-based automation, run locally over stdio via npx chrome-devtools-mcp. Hand check 2026-08-25: no MCP revision statement in README, CHANGELOG or docs; @modelcontextprotocol/sdk 1.30.0 is a devDependency of a bundled build, so the SDK chain cannot ground a revision. v1.8.0 released 2026-08-25.

• mcp-server-browserbase - Earlier Revision

  Distributed as npm:@browserbasehq/mcp-server-browserbase. Resolved from the published package: @browserbasehq/mcp-server-browserbase 2.4.3 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Playwright MCP - Spec Support Unverified

  Microsoft's Playwright MCP server: browser automation through structured accessibility snapshots rather than screenshots, run locally over stdio via npx @playwright/mcp. Hand check 2026-08-25: no MCP revision statement in the README or linked docs; @modelcontextprotocol/sdk ^1.25.2 appears only as a devDependency, so the SDK chain cannot ground a revision. Runs stdio by default, HTTP with --port.

• playwright-stealth - Earlier Revision

  Distributed as npm:playwright-stealth-mcp-server. Resolved from the published package: playwright-stealth-mcp-server 0.2.3 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Shiplight MCP - Spec Support Unverified

  Distributed as npm:@shiplightai/mcp. First-party: the ai.shiplight registry namespace is domain-verified and the server fronts Shiplight's own agent-testing platform. No public repository; the registry record and npm package carry no repo URL. No MCP revision statement found (checked 2026-08-27) on shiplight.ai or in the package README.