tabby-mcp
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_targetsA | List available CDP targets (tabs) with their index, URL, and WebSocket URL |
| execute_jsA | Execute JavaScript code in Tabby terminal context and return the result. Code is wrapped in async IIFE by default for fresh scope and await support. |
| queryA | Query DOM elements by CSS selector. Automatically waits for Angular and element to exist. |
| screenshotB | Capture screenshot of Tabby terminal window or specific element |
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 4 tools
Each tool has a clearly distinct purpose: execute_js runs code, list_targets lists tabs, query finds DOM elements, screenshot captures images. There is no overlap.
Most tools follow a verb_noun pattern (execute_js, list_targets), but 'query' and 'screenshot' are less consistent. Still, the pattern is understandable.
Four tools is appropriate for a focused automation toolkit. Each tool serves a clear function without being excessive or insufficient.
The set covers basic inspection and execution but lacks common browser actions like navigation, clicking, or typing, which limits its completeness for typical automation tasks.