MCP Browser Server
MCP Browser Server — Model Context Protocol Browser Automation
A hosted Model Context Protocol server that gives any MCP-compatible LLM a real Chrome session it can drive. Free 1,000 credits.
- Hosted endpoint: mcp.browserforhire.com — no infra to run.
- npm package: @browserforhire/mcp — for self-hosted MCP setups.
- Tools: goto, click, fill, scrape, screenshot, run_js, set_cookie, screenshot_element.
- Works with Claude Desktop, Cline, Continue, Cursor, and any MCP host.
~/.claude/mcp.jsonJSON
{
"mcpServers": {
"browserforhire": {
"command": "npx",
"args": ["-y", "@browserforhire/mcp"],
"env": {
"BFH_API_KEY": "bf_live_..."
}
}
}
}What you get
Hosted or self-host
mcp.browserforhire.com for the easy path. @browserforhire/mcp on npm if you prefer to run the bridge yourself.
Full tool surface
goto, click, fill, scrape, screenshot, run_js, set_cookie, get_cookies, screenshot_element, wait_for, evaluate.
Per-request billing
Each MCP tool call maps to one credit (or more for long sessions). No hourly buckets, no surprises.
FAQ
Can I limit which tools the agent has access to?+
Yes. Pass &allow=goto,click,scrape on the connect URL to whitelist tools per session. Useful for read-only research agents.
How do I keep the agent logged in across calls?+
Pass session=<id>. The MCP bridge auto-attaches the session token to every tool call within the host process.
Ship Chrome to production today.
Free 1,000 credits, no credit card. Drop-in replacement for Browserless.