← Back to directory
F

FSB MCP Server

Community
Control the FSB browser extension from any MCP client for DOM-first AI browser automation.
GitHub source repository ↗
★ 187 Stars Category · Browser Very popular Source revision 96bdcedc1f34
66FMRS · C
Reliability
10/20
Security and permissions
14/20
Maintenance
15/20
Documentation
15/20
Setup experience
12/20

FSB MCP Server provides powerful browser control for MCP clients, using a DOM-first architecture that outperforms vision-based approaches. It supports multiple clients and offers a rich toolset. However, it requires installing a browser extension and automation needs supervision with security considerations.

Read the FMRS scoring method →

FSB MCP Server is a local MCP server that allows external AI clients (e.g., Claude Code, Cursor, VS Code) to control the FSB Chrome extension. It exposes 66 registered tools covering manual browser control, read-only inspection, autopilot, trigger watchers, capability search/invoke, vault, and observability. The server communicates with the extension via a WebSocket bridge and supports both stdio and Streamable HTTP transports.

Tools

run_task
Run a natural language task using FSB's own automation loop.
stop_task
Stop the current running task.
get_task_status
Get the status of the current task.
back
Navigate back to the previous page.
trigger
Set a watch on a page element for future changes and report.
stop_trigger
Stop a specified trigger watch.
get_trigger_status
Get the status of a trigger watch.
list_triggers
List all active trigger watches.
execute_js
Execute safe JavaScript in the page context for DOM reads or simple clicks.
navigate
Navigate to a specified URL.
click
Perform a click on a selected selector.
type_text
Type text into an input element.
press_key
Send keyboard key events.
drag
Perform a drag operation.
upload_file
Upload a local file to a file input via CDP.
read_page
Read the current page's accessible text and structure.
get_dom_snapshot
Get a snapshot of the current DOM, including selectors and forms.
get_page_snapshot
Get a snapshot of the page, including visual and structural info.
get_site_guide
Get the site guide for the current site, including selectors and tips.
read_sheet
Read spreadsheet or table data.
search_capabilities
Search the capability catalog for available first-party API capabilities.
invoke_capability
Invoke a verified API capability.
list_sessions
List historical sessions.
get_logs
Get action logs.
search_memory
Search long-term memory.
list_credentials
List saved credentials.
fill_credential
Autofill a credential.
use_payment_method
Use a saved payment method.
start_visual_session
Start a visual session.
end_visual_session
End a visual session.

Setup

  1. Install the Chrome extension: get FSB from the Chrome Web Store.\n2. Install the MCP server: For Claude Code, run npx -y fsb-mcp-server install --claude-code; for Claude Desktop, --claude-desktop; for Cursor, --cursor; for VS Code, --vscode; for Windsurf, --windsurf; for Codex, --codex.\n3. Restart the client for the server to appear.\n4. Try a task from the client, e.g., 'Search for cats on Google'.
claude_desktop_config.json
{
  "servers": {
    "fsb": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "fsb-mcp-server"]
    }
  }
}

Fit and risk

Best for

  • Developers who want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction

Not for

  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)

Required permissions

  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths

Risks and side effects

  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks

Troubleshooting

  1. Run `npx -y fsb-mcp-server doctor` to check connection and status
  2. Run `npx -y fsb-mcp-server status --watch` to monitor extension status
  3. Ensure Chrome and the extension are open, and the active tab is a normal webpage, not a browser-internal page
  4. Restart the client to load the MCP server
  5. Check that content scripts are re-injected after extension reload

Use cases

Natural language browser automation: search, click, fill forms
QA and regression checks: repeat page flows, collect action logs
Research: navigate pages, extract visible info, summarize results
Data entry: handle structured forms, dropdowns, table inputs
Ecommerce: compare product pages, inspect prices, monitor availability
Finance and dashboards: read charts and tables
Trigger watchers: monitor page elements for changes
Developer workflows: drive GitHub, issue trackers, etc.

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support
WindsurfFull support
CodexFull support