tactab
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WS_PORT | No | The WebSocket port used by the bridge to communicate with the Chrome extension. By default, the bridge uses WebSocket port 8080. To use a different port, set the WS_PORT environment variable before launching (e.g. set WS_PORT=8090 / export WS_PORT=8090) and update the port in extension/background.js. | 8080 |
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 |
|---|---|
| automate_websiteB | Executes custom browser actions on the currently active webpage via the local Chrome extension bridge. |
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 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. Its purpose is clearly stated as executing browser actions via a Chrome extension bridge.
The single tool follows a clear verb_noun snake_case pattern (automate_website). There are no mixed conventions or naming conflicts to penalize.
A single tool is borderline thin for a browser automation server. It could be intentional as a generic executor, but the set lacks distinct operations that agents would typically expect.
The surface provides one generic action executor with no explicit operations, parameters, or lifecycle coverage. Agents lack discoverable building blocks for common browser automation tasks, creating likely gaps.