Browser Control
Related Servers
Alternatives to Browser Control
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to drive a local Firefox browser: opening and managing tabs, navigating, reading page structure and text, clicking, typing, filling forms, running JavaScript, taking screenshots, and inspecting console messages and network requests. Everything runs over a local Unix socket with no network traffic, and actions are restricted to tabs explicitly placed under Claude's control.8 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to control Firefox by listing and managing tabs, navigating, taking screenshots, reading pages, clicking and typing, and inspecting console and network activity through a local bridge.32 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real Firefox browser through a local MCP server using synthetic DOM events for clicks and typing. Supports tab management, navigation, page reading, form interaction, screenshots, and per-site consent with no network port opened.4 npm1MIT
- MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to control the user's real Firefox browser through a local MCP server, with tools for tabs, navigation, page reading, clicking, typing, forms, screenshots, and file uploads under per-site consent.4 npmMIT
- AlicenseBqualityCmaintenanceLets Claude Code attach to a running, signed-in Firefox over WebDriver BiDi to control tabs, navigate, screenshot, read pages, click, type, fill forms, evaluate JavaScript, and inspect console/network activity.22MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: tab lifecycle (open, close, reorder, group), tab/history listing, content extraction, highlighting, and screenshots. Overlap is minimal, and even the two read tools (get-tab-web-content vs capture-tab-screenshot) differ by output modality. An agent can reliably select the correct tool.
All tool names use consistent kebab-case with verb-first phrasing (open-, close-, get-, reorder-, find-, group-, capture-). Resource nouns are predictable (browser-tab, tabs, history, web-content). No mixed conventions or naming outliers.
Nine tools is well-scoped for a browser-control server and sits comfortably in the ideal 3-15 range. Each tool maps to a distinct operation, avoiding both bloat and thinness.
The surface covers core tab management, history, content extraction, highlighting, and screenshots. Minor gaps like navigating an existing tab or refreshing a page are absent, but agents can approximate these via opening a new tab or re-reading content.