browser-pool-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSER_POOL_DEBUG | No | Set to 1 to enable debug logging to debug.log | 0 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_navigateC | Navigate to URL |
| browser_snapshotD | Page snapshot |
| browser_clickD | Click element |
| browser_typeD | Type text |
| browser_screenshotD | Take screenshot |
| browser_closeC | Close browser |
| browser_tabsD | Manage tabs |
| browser_navigate_backD | Go back |
| browser_press_keyD | Press key |
| browser_hoverC | Hover element |
| browser_select_optionD | Select option |
| browser_evaluateD | Run JavaScript |
| browser_wait_forD | Wait for condition |
| browser_resizeD | Resize window |
| browser_handle_dialogD | Handle dialog |
| browser_file_uploadD | Upload files |
| browser_console_messagesD | Get console |
| browser_network_requestsC | Get network requests |
| pool_statusC | Browser pool status |
| pool_testD | Test async response |
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 20 tools
Most tools have distinct purposes targeting specific browser interactions like clicking, typing, navigating, or taking screenshots. However, 'browser_evaluate' (run JavaScript) and 'browser_snapshot' (page snapshot) could potentially overlap with other tools in functionality, creating minor ambiguity in certain scenarios.
Tool names follow a highly consistent snake_case pattern with clear 'browser_' or 'pool_' prefixes, making them predictable and readable. The verb_noun structure is maintained throughout, such as 'browser_click', 'browser_navigate', and 'pool_status', ensuring no mixing of conventions.
With 20 tools, the count is borderline heavy for a browser automation server, potentially overwhelming for agents. While it covers many interactions, some tools like 'browser_snapshot' and 'browser_screenshot' might be redundant, suggesting the set could be more streamlined without losing core functionality.
The toolset provides comprehensive coverage for browser automation, including navigation, interaction, debugging, and pool management. Minor gaps exist, such as no explicit tool for handling cookies or local storage, but agents can likely work around these using existing tools like 'browser_evaluate' for JavaScript execution.