shiftover
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| accountsA | List the pooled Claude Code accounts with their 5-hour / weekly usage windows, per-model windows, headroom and live sessions, plus the Codex CLI backend when it is installed. Read-only; uses a short cache. |
| delegateA | Run a self-contained task as a headless Claude Code session on another account (or on the OpenAI Codex CLI with account="codex") and return its answer. The delegate sees only the prompt, has no claude.ai connectors and nobody answers its permission prompts. Long tasks: background=true, then monitor. |
| monitorB | Status and results of delegate jobs. Without job_ids lists recent jobs. wait_seconds blocks for running jobs; cancel stops them. |
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 3 tools
Each tool has a clearly distinct role: accounts is read-only account listing, delegate starts a task, and monitor checks or cancels jobs. The boundary between delegate and monitor is clear because monitor explicitly handles status, results, waiting, and cancellation.
The names are readable but do not follow a single convention: accounts is a plural noun, while delegate and monitor are verbs. With only three tools this is not confusing, but the naming pattern is mixed.
Three tools is well-scoped for this server: one to inspect available accounts, one to run work, and one to track or cancel delegated jobs. Each tool earns its place without unnecessary surface area.
The surface covers the core lifecycle: list accounts, delegate a task, monitor results, wait, and cancel. Minor gaps exist around account management or more explicit job inspection, but the primary workflow is complete.