Self-hosted Playwright MCP alternatives
Playwright already runs locally. Its server drives a browser through the accessibility tree over stdio, from a process you control, and if you want to keep that property while changing what the agent does, the servers below install locally too.
Each runs as a local process. The automation logic and credentials stay on your machine or network, though anything that reaches out to a website or remote service still makes that call. The server itself is yours to operate.
The 8 best self-hosted alternatives
Installed locally, the Browserbase server drives browsers with Stagehand: start, navigate, act, observe, and extract. The browsers themselves run in Browserbase's cloud, so this is the local-server, remote-browser split.
Set up Browserbase →Anthropic's Fetch server runs locally and pulls a URL into clean markdown. The request leaves your network to reach the page, but the server process stays on your machine.
Set up Fetch →The reference Memory server keeps its knowledge graph of entities, relations, and observations on local disk. Nothing leaves your machine, which makes it fully self-contained.
Set up Memory →Time runs locally and answers current-time and IANA timezone questions with no network call. It is the simplest stdio companion for tasks that hinge on dates.
Set up Time →The community n8n server installs locally and gives an agent complete knowledge of n8n's 800+ nodes to design, validate, and deploy workflows, all from a process you run.
Set up n8n →Run the official BrowserStack server locally to execute manual and automated tests on real browsers and devices, then debug failures. The tests run on BrowserStack's grid; the server stays yours.
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.
Set up Node-RED →For durable, long-running automation, the Temporal server runs locally and manages workflows, signals, queries, batch operations, and schedules in your own cluster.
Set up Temporal →
How to choose
Every server here runs as a local process, which is what Playwright already gives you. Browserbase and BrowserStack keep the server local while the actual browsers run in their clouds; n8n, Node-RED, and Temporal stay fully local for orchestration. Fetch reaches out to read pages, and Memory and Time make no outbound calls at all.
FAQ
- Is the Playwright MCP server self-hosted?
- Yes. Playwright runs as a local stdio process and drives a browser on your own machine. It has no hosted endpoint, so self-hosting is the only way it runs.
- Does running the server locally mean nothing leaves my network?
- Not always. The server process stays local, but browser automation still loads remote pages, and Browserbase and BrowserStack run the actual browsers in their clouds. Memory and Time are the fully self-contained options here.