Browser Task Runner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BTR_DATA_DIR | No | Where runs, logs and the bridge token are written (default: the repo folder) | |
| BTR_HEADLESS | No | Set to 1 to launch the browser set in BTR_CHROME_PATH in headless mode | |
| BTR_TRANSPORT | No | Batch transport: cdp (default when a browser is configured), node, or bridge | |
| BTR_ALLOW_HOSTS | No | Extra hosts the tools may touch, comma separated. *.example.com allowed. localhost is always allowed | |
| BTR_BROWSER_URL | No | Attach to a running browser, e.g. http://127.0.0.1:9222 | |
| BTR_CHROME_PATH | No | Or launch this browser executable (BTR_HEADLESS=1 for headless; with BTR_USER_DATA_DIR as its profile) | |
| BTR_WS_ENDPOINT | No | Or attach by its WebSocket endpoint | |
| BTR_USER_DATA_DIR | No | Or attach through a profile's DevToolsActivePort file | |
| BTR_ALLOW_EVALUATE | No | Set to 1 to offer the evaluate tool. Off by default; every call still needs confirm: true | |
| BTR_EXTENSION_ORIGIN | No | Pin the bridge to one extension, e.g. chrome-extension://<extension id> |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues