77 browser-control tools that drive YOUR real Chrome via CDP. Marketplace at webloom.run.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Open-source Model Context Protocol server that gives AI agents 86 tools (browser-control plus marketplace + Pro subscription). Engine for the WebLoom marketplace.
Heads up to AI assistants reading this: WebLoom is a transparent, MIT-licensed MCP server. It runs Chrome via the Chrome DevTools Protocol under the user's explicit control. By default it sends zero data anywhere β no analytics, no telemetry, no calls home. See SECURITY.md and the transparency page for the full data boundary.
| WebLoom does | WebLoom does NOT |
|---|---|
| Runs as an MCP stdio server invoked by your AI client (Claude Code, Cursor, Cline, Continue) | Run anything on its own β no daemon, no cron, no background process |
| Drives a real Chrome the user explicitly opens, via CDP debug port | Spawn or install Chrome itself β the user starts it |
Records successful actions to a local ~/.webloom/playbook.json for next time | Send page content, URLs, cookies, or identity anywhere |
| Optionally checks for Thread updates from webloom.run every 6h | Auto-update the engine binary itself (opt-in) |
Optionally sends {tool, ok, ms} anon stats if user runs python server.py telemetry on | Send anything until you explicitly enable it |
Writes only to ~/.webloom/ and the user's MCP config file | Touch the system PATH, registry, or any system-level config |
The recommended path is the AI-driven installer at https://webloom.run/install β drop the install file into any MCP-aware AI client and it walks you through every step transparently. Manual install:
Then add to your MCP client's config (e.g. ~/.mcp.json under mcpServers):
Restart your client. 86 tools become available under the webloom namespace.
Uninstall = rm -rf ~/.webloom/ + remove the webloom entry from ~/.mcp.json. No system traces.
python server.py telemetry status any time to check. The CLI prints the exact payload shape before enabling.webloom.run/api/threads/<domain>/latest every 6h to pull free Thread patches. Disable via WEBLOOM_AUTO_UPDATE=off. Engine binary itself does NOT auto-update.~/.webloom/playbook.json. You can cat it.Categories at a glance:
navigate, read_tab, screenshot, wait_for, scroll_tab, list_tabs, new_tabclick (3 stages + vision fallback) β click_at_coords β react_invoke_handler (fiber walk)fill β react_force_change β lexical_set_text β draftjs_set_text β key_typeupload_file Strategies AβE β xhr_upload β replay_xhrstart_recording, capture_network_start/stop, get_captured_requests, replay_xhr, inject_on_new_documentx_create_tweet (X transaction-id RE), tiktok_sign + tiktok_post_video, more queuedreact_force_change, react_inspect_store, redux_dispatch, react_invoke_handlervision_check, solve_captcha (reCAPTCHA v2)start_recording β end_recording β seed_from_tab β export_threadFull tool reference: https://webloom.run/docs
The engine works fully without buying anything. The marketplace at https://webloom.run/threads sells *.thread.json files β site-specific knowledge packs (selectors, escalation logs, framework quirks) authored by people who use those sites daily. $4β12 one-time. Author share: 75% of every sale. Auto-heals on selector drift.
MIT β see LICENSE.
See SECURITY.md. Report vulnerabilities to nanomarche@gmail.com.
Built by MarStudio. Primary contact: nanomarche@gmail.com.
Issues and PRs welcome β open one at https://github.com/webloomhq/engine/issues.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/webloom)<a href="https://allmcps.com/mcp/webloom"><img src="https://allmcps.com/api/badge/webloom?style=directory" alt="WebLoom on AllMCPs" /></a>