Browser Agent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_BROWSER_TYPE | No | The browser type to use. Supported values: chrome (default), firefox, webkit, edge | chrome |
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_set_viewportA | Change the browser's viewport size and scale factor |
| browser_navigateC | Navigate to a specific URL |
| browser_screenshotB | Capture a screenshot of the current page or a specific element |
| browser_clickC | Click an element on the page |
| browser_fillB | Fill a form input with text |
| browser_selectC | Select an option from a dropdown menu |
| browser_hoverC | Hover over an element on the page |
| browser_evaluateB | Execute JavaScript in the browser context |
| api_getC | Perform a GET request to an API endpoint |
| api_postB | Perform a POST request to an API endpoint |
| api_putC | Perform a PUT request to an API endpoint |
| api_patchB | Perform a PATCH request to an API endpoint |
| api_deleteB | Perform a DELETE request to an API endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: API tools are differentiated by HTTP method, and browser tools cover unique interactions like clicking, hovering, filling, etc. No two tools overlap in function.
All tools follow a consistent '<domain>_<action>' pattern, with 'api_' prefix for HTTP methods and 'browser_' prefix for browser actions. Naming is unambiguous and predictable.
13 tools is well-scoped for a browser automation and API testing server. Each tool covers a fundamental operation without unnecessary bloat or gaps.
Core browser interactions (navigation, clicking, form filling, selecting, screenshot) and all major HTTP methods are covered. Minor omissions like file upload or wait-for-element are acceptable for this scope.