Browser Control
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXTENSION_PORT | No | Port used by the daemon for the extension WebSocket connection (default 8089). | |
| EXTENSION_SECRET | Yes | Secret from the extension options (required). |
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 |
|---|---|
| open-browser-tabB | Open a new tab in the user's browser (useful when the user asks to open a website) |
| close-browser-tabsC | Close tabs in the user's browser by tab IDs |
| get-list-of-open-tabsC | Get the list of open tabs in the user's browser. Use offset and limit parameters for pagination when there are many tabs. |
| get-recent-browser-historyB | Get the list of recent browser history (to get all, don't use searchQuery) |
| get-tab-web-contentA | Get the full text content of the webpage and the list of links in the webpage, by tab ID. Use "offset" only for larger documents when the first call was truncated and if you require more content in order to assist the user. |
| reorder-browser-tabsC | Change the order of open browser tabs |
| find-highlight-in-browser-tabC | Find and highlight text in a browser tab (use a query phrase that exists in the web content) |
| group-browser-tabsC | Organize opened browser tabs in a new tab group |
| capture-tab-screenshotA | Capture a screenshot of the visible area of a browser tab, by tab ID. The user must authorize each tab by clicking the extension's toolbar button while that tab is open. If the tab is not authorized, this tool returns an error explaining what to ask the user to do; relay that request to the user and retry afterwards. Authorization ends when the tab navigates or closes. Capturing brings the tab to the foreground momentarily. |
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 9 tools
Each tool has a clearly distinct purpose: tab lifecycle (open, close, reorder, group), tab/history listing, content extraction, highlighting, and screenshots. Overlap is minimal, and even the two read tools (get-tab-web-content vs capture-tab-screenshot) differ by output modality. An agent can reliably select the correct tool.
All tool names use consistent kebab-case with verb-first phrasing (open-, close-, get-, reorder-, find-, group-, capture-). Resource nouns are predictable (browser-tab, tabs, history, web-content). No mixed conventions or naming outliers.
Nine tools is well-scoped for a browser-control server and sits comfortably in the ideal 3-15 range. Each tool maps to a distinct operation, avoiding both bloat and thinness.
The surface covers core tab management, history, content extraction, highlighting, and screenshots. Minor gaps like navigating an existing tab or refreshing a page are absent, but agents can approximate these via opening a new tab or re-reading content.