unified-browser-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_browserC | Launch a new browser instance with DevTools monitoring enabled |
| navigateC | Navigate to a URL |
| start_monitoringC | Start capturing network requests, console messages, and other DevTools data |
| fill_form_fieldC | Fill a form field with a value |
| click_elementC | Click an element |
| submit_formC | Submit a form |
| get_network_requestsB | Get all captured network requests with full headers and bodies |
| get_console_messagesC | Get all captured console messages |
| screenshotB | Take a screenshot of the current page |
| evaluate_scriptB | Execute JavaScript in the page context |
| get_performance_metricsB | Get page performance metrics from Navigation Timing API |
| stop_monitoringB | Stop monitoring and return summary |
| close_browserB | Close the browser and cleanup |
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 13 tools
Each tool targets a distinct action or data source: browser lifecycle (launch/close), navigation, interaction (click/fill/submit/script), monitoring (console/network/performance), and screenshot. No overlapping purposes.
All tool names follow a consistent snake_case verb_noun pattern (e.g., click_element, get_console_messages, launch_browser), making the set predictable and easy to understand.
13 tools cover the essential operations for browser automation without being excessive. Each tool serves a clear role, and the count feels well-scoped for the domain.
Core workflows (navigate, interact, monitor, screenshot) are covered. Minor gaps exist, such as no direct tool for getting page source or managing cookies, but evaluate_script can compensate.