Firefox Browser Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_network_requestsB | List captured network requests from Firefox. Filterable by URL regex pattern, HTTP method, status code, and content type. Returns newest first. |
| get_request_detailsA | Get full details of a specific captured request: headers, request body, response body, timing. |
| search_networkA | Full-text search across all captured request URLs, headers, and bodies. |
| get_page_infoA | Get the current active tab's URL, title, and tab ID. If a monitored tab is set in the extension popup, returns that tab's info. |
| query_domA | Query DOM elements on the current page by CSS selector. Returns tag, text content, attributes, and outerHTML for up to 50 matching elements. |
| get_page_htmlA | Get the full page HTML or a specific element's HTML. Truncated at 500KB. |
| get_console_logsB | Get recent console log entries from the current page. Only available after the first query triggers injection. |
| get_screenshotA | Capture a screenshot of the current (monitored) tab. Returns a PNG by default, or JPEG to reduce size. |
| get_storageA | Get the current page's localStorage, sessionStorage, and cookies (including HttpOnly cookies). Useful for debugging auth/session state. Large values are truncated. |
| get_capture_statusA | Diagnose what the extension is actually capturing right now: connection state, monitored tab, capability toggles, whether the network/console/XHR hooks are present on the current tab (e.g. blocked by CSP), and buffer counts. Use this when a capture tool unexpectedly returns nothing. |
| navigateA | Navigate the monitored tab to a URL (http/https only). Requires the 'interact' capability to be enabled in the popup. |
| reloadA | Reload the monitored tab. Requires the 'interact' capability. |
| clickB | Click the first element matching a CSS selector on the monitored tab. Requires the 'interact' capability. |
| fillA | Set the value of an input, textarea, select, or contenteditable element matching a CSS selector and fire input/change events. Requires the 'interact' capability. |
| start_ws_captureA | Start capturing WebSocket frames for connections matching the given URL pattern. Frames are NOT captured by default — call this first to enable capture. |
| stop_ws_captureA | Stop capturing WebSocket frames for the given URL pattern. |
| get_ws_framesB | Get captured WebSocket frames. Must call start_ws_capture first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct aspect of browser debugging: network requests, DOM, console, storage, interaction, and WebSocket. Even tools dealing with similar domains (e.g., get_network_requests vs. search_network) have clearly differentiated purposes.
Naming mostly follows a verb_noun pattern with snake_case, but there is some inconsistency: some tools start with 'get_' while others are bare verbs like 'navigate' or 'click'. However, the pattern is clear and readable.
17 tools is well-scoped for a browser automation/debugging bridge, covering network, DOM, storage, console, screenshots, WebSocket, navigation, and interaction without being overwhelming.
The tool set covers nearly all essential operations for inspecting and controlling a Firefox tab: capturing network requests (including WebSocket), querying/modifying DOM, reading storage, taking screenshots, and interacting with the page. Missing capabilities like keyboard events are minor.