Browser MCP — control your real Chrome from Claude Code. 29 tools: CAPTCHA solving, file upload, multi-session, human...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
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 unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if browser-mcp 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/Agent360dk/browser-mcp ~/.claude/agents/browser-mcpRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/browser-mcpNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ browser-mcp/ ← installs here └─ settings.json
Browser MCP — control your real Chrome from Claude Code. 29 tools: CAPTCHA solving, file upload, multi-session, human-in-the-loop. browsermcp.dev