Doctor first protocol
Runs npx -y fsb-mcp-server doctor, parses the failing layer (one of package, bridge, extension, active-tab, content-script, config), and prints the next step recommendation. Exit code surfaces failure to the host.
OpenClaw ReadyGive your agent a real browser.
FSB ships a polished OpenClaw skill plus a 66-tool MCP surface that any agent runtime can drive. Click, type, orchestrate across tabs, fill vault credentials, read live page state, all from one prompt, in the user's actual Chrome.
Meet the FSB Skill
The canonical OpenClaw onboarding path for FSB. Loads cleanly into a fresh OpenClaw, runs the full diagnostic flow, and installs the bridge for any other MCP host on your machine.
Stdio config printer
Emits the canonical OpenClaw stdio block to paste into your MCP config. The block stays parity locked with mcp/src/install.ts so the printer never drifts from the rest of the installer.
Consent gated host install
Detects other MCP hosts (Claude Desktop, Cursor, Codex, etc.) and asks y/n per host before installing. Never --all without consent. Never auto writes the OpenClaw config.
Why FSB MCP is powerful
Browser automation usually means a headless instance you cannot see. FSB drives the user's actual Chrome session, and the MCP surface is built around four hard requirements: precision, observability, safety, and concurrency.
66
MCP tools, one surface
Read, click, type, navigate, vault, observe. All typed. All agent-scoped. One surface, no glue code.
N agents
Multi agent identity and tab ownership
Server-minted agent_id per session. Tabs owned per agent. Cross-agent calls fail loud with TAB_NOT_OWNED. Cap 1-64 (default 8), AGENT_CAP_REACHED when full. No focus stealing.
0 leaks
Vault boundary, by design
Passwords and cards resolve inside the extension's encrypted store via fill_credential and use_payment_method. Never in chat. Never in args. requires.env is mandatory empty.
Live
Real Chrome, real session
Your cookies. Your extensions. Your saved state. change_report streams mutations on every action — no extra read_page round-trip.
Where FSB earns its keep
The recurring browser work. The boring, repetitive stuff that vision-based agents struggle with on logged-in sites. FSB runs in the user's real Chrome, so cookies, sessions, MFA state, and saved logins are already there.
Open Gmail, label everything from billing as finance, draft replies to support threads using yesterday's tone, and flag anything urgent.
In Zendesk, draft answers to open tickets about pricing, order status, and shipping using the help center as ground truth.
Pull yesterday's revenue, signups, and refund count from the analytics dashboard and post a one paragraph summary.
Score new LinkedIn connection requests against the ICP, draft outreach for the top three, and skip the rest.
Categorize today's invoices in the POS as supplies vs. retail, extract shipping line items, and flag any vendor over last month's average.
These run as manual-mode tool calls. Autopilot (run_task) only fires when the user explicitly delegates the whole task -- "use FSB autopilot", "delegate this", or names run_task directly. Manual mode is the default for everything else.
Ship a real browser to your agent today.
Free, open source, BYO model keys. Works with OpenClaw, Claude, Codex, Cursor, Windsurf, and any MCP host that speaks the OpenAI tool protocol.