Self-hosted Browserbase MCP alternatives
Browserbase's server installs locally and runs over stdio; the sessions it drives are cloud browsers, but the server process and your credentials stay on your own machine. If you are comparing local servers, every option below also installs and runs on infrastructure you control.
One honest distinction: Browserbase drives browsers in the cloud, so even self-hosting the server sends page interaction to its hosted browsers. Playwright is the pick if you want the browser itself local too. The rest cover reading, automation, and testing from a local process.
The 8 best self-hosted alternatives
Playwright's official server runs locally and drives a local browser through the accessibility tree, with browser_navigate, browser_click, browser_type, and browser_fill_form. It keeps both the server and the browser on your own machine, unlike Browserbase's cloud sessions.
Set up Playwright →Anthropic's reference Fetch server installs locally and pulls a URL into clean markdown. It reads pages rather than driving them, so reach for it from your own process when an agent needs page text and not a live, interactive session.
Set up Fetch →The reference Memory server runs locally and keeps a persistent knowledge graph of entities, relations, and observations. It does not touch a browser; keep it beside a driver so an agent remembers findings across sessions from a process you control.
Set up Memory →Current-time lookups and timezone conversion via get_current_time and convert_time are all the reference Time server does, locally. It is a small local utility an agent uses while automating, not a browser tool in its own right.
Set up Time →The community n8n server runs locally and gives an agent complete knowledge of n8n's 800+ nodes to design, validate, and deploy workflows. It builds automations on your own infrastructure rather than driving a live browser.
Set up n8n →BrowserStack's server installs locally and runs manual and automated tests on real browsers and devices, debugging the failures. Like Browserbase it reaches real browsers, but for test runs, with the server process kept on your machine.
Set up BrowserStack →Node-RED's server runs locally and lets an agent read, build, and update flows, manage nodes, trigger inject nodes, and inspect runtime state via the Admin API. It is flow-based automation you operate yourself, with web steps living inside a flow.
Set up Node-RED →Durable execution is Temporal's domain: this server manages workflows, signals, queries, batch operations, and schedules in your own cluster. It orchestrates long-running automations locally rather than driving a browser, fitting reliable multi-step jobs.
Set up Temporal →
How to choose
For a fully local browser, Playwright is the standout, keeping both server and browser on your machine where Browserbase still drives cloud sessions. Fetch covers read-only page access. BrowserStack reaches real browsers for testing. n8n, Node-RED, and Temporal are local automation and orchestration platforms, and Memory and Time are small utilities beside whichever driver you choose.
FAQ
- Can the Browserbase MCP server be self-hosted?
- The server itself installs locally over stdio, so the process and credentials stay on your machine. The browser sessions it drives still run in Browserbase's cloud. If you want the browser local too, Playwright drives a local browser from a local server.
- Which self-hosted alternative keeps the browser on my own machine?
- Playwright. It runs locally and drives a local browser through the accessibility tree, so nothing about the session leaves your infrastructure. BrowserStack reaches real browsers for testing, and Browserbase uses cloud sessions even when its server is self-hosted.