Log inSubmit server
FSB logo

FSB

by fullselfbrowsing

Drive a signed-in Chrome session through MCP using DOM-based browser automation, action verification, triggers, and session logs.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install FSB

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fullselfbrowsing-fsb": {
      "command": "npx",
      "args": [
        "-y",
        "fsb-mcp-server@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 72 tools correctly (Today).

Overview

fullselfbrowsing/FSB connects MCP clients to a signed-in Chrome session through a Chrome extension and local MCP server. It reads the live DOM, selectors, ARIA data, and forms instead of relying on screenshots, then executes browser actions, verifies results, waits for page changes, and reports progress. MCP use does not require an FSB API key because the connected client provides the model reasoning. Reach for it when supervised research, testing, form entry, page inspection, or browser-based developer workflows need access to an existing Chrome session.

Use cases

  • Run repeatable QA and regression flows
  • Research pages and summarize visible information
  • Fill structured forms and browser-based data-entry workflows
  • Compare products and monitor availability under supervision
  • Inspect DOM structure and accessibility-related controls

Key features

  • DOM-first browser control
  • 69 registered MCP tools
  • Action verification and smart waiting
  • Supervised local file uploads
  • Page-element trigger watchers
  • Session logs and workflow memory

Tools72

What FSB lets your agent do. Expand a tool for its parameters.

Verified live~28.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

What it can do

From the 72 tools this server returned when we ran it.

Runs commands · 3Can delete or modify data · 3Writes files · 1Handles credentials · 7Makes network requests · 42Read-only tools · 65
Unusual tool instructions. 1 tool description contain text aimed at the AI model rather than at you (reaches for local secrets). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age212 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8h ago via OSV.dev · fsb-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars202Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed72Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How FSB works

What fullselfbrowsing/FSB MCP server does

fullselfbrowsing/FSB lets an MCP client operate a Chrome browser through the FSB extension. The browser side exposes the current page structure, including DOM content, element references, selectors, forms, and ARIA labels. Agents can use that structure to navigate pages, interact with controls, enter data, inspect results, and summarize visible information.

The project describes 69 registered MCP tools, built from 57 shared definitions: 53 browser tools and four trigger tools, with additional MCP-facing registrations. Its browser workflow includes DOM snapshots, action-result checks, smart waiting, stuck-state detection, visual feedback, and session logs. It also includes supervised file uploads, long-term memory for sites and workflows, and credential and payment vault flows.

How it works

The MCP server acts as the connection between an external MCP client and the Chrome extension. After the extension is installed and the MCP server is configured for a client, commands from the model are carried out in the open Chrome session. The extension reads the page’s live structure rather than sending screenshots to the model, which suits tasks based on page elements, forms, tables, labels, and controls.

FSB can run tasks from an MCP client or directly from the extension’s popup and side panel. The standalone extension mode supports xAI, Gemini, OpenAI, Anthropic, OpenRouter, LM Studio, and custom OpenAI-compatible endpoints. MCP operation does not require an FSB API key.

Setup and configuration

Install the browser component from the Chrome Web Store, then install the MCP server for the client you use. The project provides these setup commands:

  • Claude Code: npx -y fsb-mcp-server@latest install --claude-code
  • Claude Desktop: npx -y fsb-mcp-server@latest install --claude-desktop
  • Cursor: npx -y fsb-mcp-server@latest install --cursor
  • VS Code: npx -y fsb-mcp-server@latest install --vscode
  • Windsurf: npx -y fsb-mcp-server@latest install --windsurf
  • Codex: npx -y fsb-mcp-server@latest install --codex

Use --all to install for all listed clients, or add --dry-run to preview changes. npx -y fsb-mcp-server@latest doctor performs a setup check. Restart the MCP client after installation so the server becomes available.

The extension and Chrome must remain available while the client drives the browser. For direct extension use, configure a supported model provider and API key in the extension settings instead of using MCP.

Tools and capabilities

  • Inspect live DOM structure, selectors, forms, and ARIA labels.
  • Navigate pages and interact with links, buttons, inputs, dropdowns, custom controls, and tables.
  • Verify actions, wait for page changes, detect stuck states, and record session activity.
  • Upload local files through the supervised upload_file tool with sensitive-path safeguards.
  • Monitor page elements for changes, thresholds, or availability through trigger tools.
  • Search a capability catalog and invoke verified, signed, audited first-party API capabilities subject to denylist controls.
  • Retain memory about sites, workflows, selectors, and task outcomes.

Limitations and notes

FSB is intended for supervised browser automation. Complex or sensitive sites can still produce unpredictable behavior, so actions should be monitored and tested on non-critical pages first. It is designed around page structure and user actions rather than visual screenshots, and is not intended as a stealth browser, scraper farm, or unsupervised account operator.

Background agents and scheduled or recurring automation are no longer active features. Existing background-agent data in Chrome storage is retained for users who had older agents.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about FSB

fullselfbrowsing/FSB is an MCP server that connects MCP clients to a signed-in Chrome session through its browser extension and local bridge. Its main tools inspect the live DOM, navigate pages, perform browser actions, verify results, wait for changes, upload files under supervision, and monitor page elements with trigger tools.

Install it with the client-specific `npx` command, such as `npx -y fsb-mcp-server@latest install --cursor` for Cursor. Install the FSB Chrome extension separately, run the `doctor` command if needed, and restart the MCP client after setup.

Yes, fullselfbrowsing/FSB provides a Cursor installer command: `npx -y fsb-mcp-server@latest install --cursor`. The Chrome extension must also be installed so the MCP bridge can reach the browser session.

No API key is required when an MCP client drives FSB because the client’s model handles the reasoning. Direct use from the extension popup or side panel requires an API key for a supported provider or compatible endpoint.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFSB AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fullselfbrowsing-fsb?style=directory)](https://allmcps.com/mcp/fullselfbrowsing-fsb)
HTML Embed
<a href="https://allmcps.com/mcp/fullselfbrowsing-fsb"><img src="https://allmcps.com/api/badge/fullselfbrowsing-fsb?style=directory" alt="FSB on AllMCPs" /></a>