browsermcp
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_navigateB | Navigate to a URL |
| browser_go_backA | Go back to the previous page |
| browser_go_forwardA | Go forward to the next page |
| browser_snapshotA | Capture accessibility snapshot of the current page. Use this for getting references to elements to interact with. |
| browser_clickB | Perform click on a web page |
| browser_hoverC | Hover over element on page |
| browser_typeB | Type text into editable element |
| browser_select_optionB | Select an option in a dropdown |
| browser_press_keyB | Press a key on the keyboard |
| browser_waitB | Wait for a specified time in seconds |
| browser_get_console_logsA | Get the console logs from the browser |
| browser_screenshotC | Take a screenshot of the current 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 12 tools
Each tool has a distinct action (click, hover, type, navigate, etc.) with no overlap. Even similar actions like go_back and go_forward are clearly differentiated by direction.
All tools follow a consistent `browser_<verb>` pattern in snake_case. The verbs are intuitive and match the action (e.g., browser_navigate, browser_type).
12 tools is appropriate for browser automation, covering navigation, interaction, screenshots, and debugging without being overwhelming or sparse.
The set covers core browsing interactions and debugging. Missing a refresh or scroll action, but most essential workflows are possible.