Bridge local MCP clients to browser WebMCP tools through Playwright, using native WebMCP when available and injected...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 62/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if webmcp-bridge belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/holon-run/webmcp-bridge ~/.claude/agents/webmcp-bridgeRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/webmcp-bridgeNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ webmcp-bridge/ ← installs here └─ settings.json
Bridge local MCP clients to browser WebMCP tools through Playwright, using native WebMCP when available and injected adapters when not.