Skip to main content
Glama
fullselfbrowsing

FSB (Full Self-Browsing)

Official
by fullselfbrowsing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to FSB (Full Self-Browsing)

No user-submitted related servers found.

    Related Servers

    • byob

      RafaelRoussel
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.
      3 npm
      ISC

    • byob

      uqgtzarhna
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents drive the real, already-logged-in Chrome browser through a companion extension, navigating tabs, clicking, typing, reading pages, filling forms, taking screenshots, and inspecting cookies, storage, console and network traffic. It keeps all communication on the local machine, with no remote-debugging port to expose and no separate headless browser or manual cookie copying to set up.
      3 npm
      ISC

    • byob

      rezende5823
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive your own already-logged-in Chrome through a browser extension, rather than a headless or cookie-copied instance. It exposes 25 tools for snapshotting pages, clicking, typing, reading content, taking screenshots, recording network traffic, and reading cookies or storage, so agents can act on authenticated sites without triggering bot detection.
      3 npm
      ISC

    • byob

      daikihunter
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.
      3 npm
      ISC

    • byob

      henrykang07945
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.
      3 npm
      ISC

    • byob

      Panagiotisu0227
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.
      3 npm
      ISC
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 72 tools

    Disambiguation3/5

    Most tools target distinct actions, but there are real overlaps: go_back and back both perform browser back navigation (with the latter even documenting conflicting history semantics), and get_page_snapshot vs get_dom_snapshot both promise 'structured refs before interaction.' The very verbose descriptions largely disambiguate these (e.g. click vs click_at, drag vs drag_drop vs drag_variable_speed), but an agent still faces genuine misselection risk among the snapshot and history tools.

    Naming Consistency4/5

    The set is overwhelmingly snake_case verb_noun (navigate, list_tabs, get_dom_snapshot, fill_credential), which is predictable and readable. Minor deviations exist—bare verbs like trigger, back, refresh, hover, search, and the slightly irregular check_box—but nothing crosses into mixed-convention chaos.

    Tool Count2/5

    72 tools is far beyond a comfortable surface for a single server, even a broad browser-automation one, and it also carries two dead tools (start_visual_session, end_visual_session marked REMOVED). The breadth is partly justified by spanning navigation, DOM, tabs, triggers, sessions, memory, credentials, payments, and capabilities, but the count is excessive and increases selection overhead.

    Completeness4/5

    Coverage is unusually thorough—navigation, interaction, DOM reading/manipulation, tabs, triggers, session/replay/log inspection, memory, credentials, payments, spreadsheets, and a capability catalog are all present with lifecycle signal tools (complete_task/partial_task/fail_task). The main blemish is the pair of removed visual-session tools still lingering in the surface rather than a true functional gap.

    Resources