Firefox MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_firefox_multiC | Launch Firefox browser with multi-tab support and debugging |
| create_tabC | Create a new tab with isolated session and debugging |
| list_tabsB | List all active tabs |
| close_tabC | Close a specific tab |
| navigateC | Navigate to a URL |
| clickD | Click on an element |
| type_textC | Type text into an input field |
| send_keyD | Send keyboard events |
| dragD | Perform drag operation |
| execute_scriptC | Execute JavaScript in the browser |
| screenshotC | Take a screenshot |
| get_page_contentC | Get HTML content |
| get_page_textC | Get visible text content |
| wait_for_elementC | Wait for element to appear |
| close_browserA | Close browser and all tabs |
| get_current_urlC | Get current page URL |
| backD | Navigate back |
| forwardC | Navigate forward |
| reloadD | Reload page |
| set_active_tabD | Set active tab |
| get_console_logsC | Get captured console logs from browser |
| get_javascript_errorsC | Get captured JavaScript errors |
| get_network_activityC | Get captured network requests and responses |
| get_websocket_messagesC | Get captured WebSocket messages (for LiveView debugging) |
| get_performance_metricsC | Get performance metrics (timing, memory usage) |
| start_monitoringC | Start/restart monitoring for a tab |
| clear_debug_buffersC | Clear debug event buffers for a tab |
| get_all_debug_activityC | Get combined feed of all debug events |
| inject_debugging_helpersC | Inject debugging helper functions into the page |
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 29 tools
Most tools have distinct purposes, but some overlap exists between click, send_key, and type_text for user input actions, and between get_page_content and get_page_text for content extraction. The descriptions help clarify differences, but an agent might occasionally misselect between these similar tools.
Tool names follow a consistent snake_case pattern with clear verb_noun structures throughout, such as navigate, get_current_url, and create_tab. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 29 tools, the count feels heavy for a browser automation server, bordering on excessive. While the tools cover many aspects, some could potentially be consolidated or omitted without losing functionality, making the set slightly overwhelming for its scope.
The tool set provides comprehensive coverage for browser automation and debugging, including navigation, tab management, content extraction, user interactions, monitoring, and debugging features. There are no obvious gaps; agents can perform full workflows from launching the browser to analyzing performance and errors.