WebLoom runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 Jun 2026.
86 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run.
What the code does
We read the source, 18 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.
r = subprocess.run([str(PUBLISHER_EXE)] + cmd, cwd=HERE)
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 WebLoom
same job, measured the same wayLets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
MCP server that drives the real Chrome you already use, through an extension and CDP.
MCP server that drives the user's real macOS Chrome via AppleScript. 32 tools.
Drive your real, logged-in Chrome/Edge from AI agents over CDP. Faster. Sharper.
Browse your real profile: -30% tokens, -25% cost, -41% tool calls, -34% tool defs, +40% faster
Debug PWAs in your real browser via MCP: service-worker, cache, installability & framework state.
WebLoom — questions
Answers built from our own checks of this server.