worktree-orbit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKTREE_ORBIT_ROOT | Yes | The root directory that worktrees must stay inside. |
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 |
|---|---|
| inspect_worktree_topologyA | Summarize local Git worktree topology, clean or dirty state, detached worktrees, locks, and prunable entries without exposing paths, branch names, hashes, remotes, or content. |
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
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly described, making selection unambiguous.
The tool name 'inspect_worktree_topology' follows a clear verb_noun pattern in snake_case, which is consistent and predictable. As a single tool, it sets a clear convention.
The server has only one tool, which is on the low end of typical tool counts. While the narrow scope of inspection might justify a single tool, the server name suggests a broader worktree management capability, making the count feel slightly thin.
The tool provides a comprehensive inspection summary, but lacks any management operations (create, delete, prune, etc.) that the server name 'worktree-orbit' implies. This leaves significant gaps in the tool surface for full worktree lifecycle coverage.