MCP Browser runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 May 2026.
Native macOS browser exposing an MCP server so AI agents can drive a real WKWebView.
What the code does
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
let process = Process()
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to MCP Browser
same job, measured the same wayReal signed-browser automation for AI agents, over a local stdio MCP server.
MCP server for Safari DevTools — browser debugging and automation for AI coding agents
MCP server for browser automation with AI agent
Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues.
End-to-end tests from one sentence: an agent drives a real browser, and passing runs replay free.
MCP server for Next AI Draw.io - AI-powered diagram generation with real-time browser preview
macOS-only MCP server for the Arc browser: tabs, navigation, page reading, DOM, scripting
MCP server + Chrome extension for AI browser control with real sessions.
MCP Browser — questions
Answers built from our own checks of this server.