Browser Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_WS_PORT | No | WebSocket port, defaults to 7483 | 7483 |
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_statusA | Check if the Chrome extension is connected and get active tab info |
| browser_navigateB | Navigate a browser tab to the specified URL |
| browser_screenshotB | Capture a screenshot of the visible area of a browser tab |
| browser_evaluateB | Execute JavaScript in the context of a browser tab and return the result |
| browser_clickB | Click an element on the page identified by a CSS selector |
| browser_fillB | Fill a form field with the specified value |
| browser_get_contentA | Get the HTML or text content of a page or specific element |
| browser_get_tabsA | List all open browser tabs |
| browser_get_consoleB | Get captured console log entries from a tab |
| browser_wait_forB | Wait for an element matching a CSS selector to appear on the page |
| browser_send_messageC | Send a custom message to the Chrome extension for extensibility |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| browse | Interact with the browser — navigate, click, fill forms, take screenshots, run JS, read page content |
| qa-runner | Run structured QA checklists against a running app via browser automation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose, such as navigating, clicking, filling, taking screenshots, evaluating JavaScript, etc. There is no overlap or ambiguity between tool functions.
All tools follow a consistent 'browser_<verb>' pattern (e.g., browser_navigate, browser_click), making the naming predictable and easy to understand.
With 11 tools, the server covers essential browser automation actions without being overwhelming. The count is well-scoped for the domain.
The tool set covers core browser operations (navigation, content retrieval, interaction, screenshots, JavaScript evaluation, tab listing, waiting, console logs). However, minor gaps like back/forward navigation, tab closing, or cookie management are missing, which prevents a perfect score.