BrowserPilot
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 |
|---|---|
| browser_navigateC | Navigate to URL |
| browser_navigate_backA | Navigate back to previous page |
| browser_snapshotB | Capture page accessibility snapshot |
| browser_take_screenshotB | Take screenshot of page or element |
| browser_clickC | Click element |
| browser_typeC | Type text into element |
| browser_hoverC | Hover over element |
| browser_press_keyC | Press keyboard key |
| browser_dragC | Drag and drop element |
| browser_select_optionB | Select option(s) in dropdown |
| browser_fill_formB | Fill multiple form fields at once |
| browser_evaluateB | Execute JavaScript in page context. Supports both function form "() => expression" and direct expression "document.title". Returns the evaluation result. |
| browser_console_messagesC | Get console messages |
| browser_network_requestsC | Get network requests |
| browser_tabsD | Manage browser tabs |
| browser_wait_forD | Wait for condition |
| browser_resizeC | Resize browser window |
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 17 tools
Each tool targets a distinct browser action or data source: navigation, input, state capture, console/network inspection, tab management, and waiting. Even similar-looking tools like browser_snapshot and browser_take_screenshot are clearly separated by accessibility tree vs visual image.
All tools share a consistent browser_ prefix and snake_case style, which makes the set feel uniform. However, naming mixes verb-phrases like browser_navigate and browser_click with noun-phrases like browser_console_messages, browser_snapshot, and browser_tabs.
At 17 tools, the set is slightly above the typical 3-15 sweet spot, but the breadth is justified by browser automation needs: navigation, mouse/keyboard input, form handling, screenshots, network/console inspection, and tab management all require separate primitives.
The tool surface covers the core browser automation lifecycle well: navigate, interact, inspect, wait, and manage tabs. Obvious gaps like browser_reload, browser_close, or cookie management are minor because they can be worked around with browser_evaluate or the existing tab management tools.