Agent Context Hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVICE_TOKENS | No | Comma-separated list of device tokens for client authentication (optional in local mode, required in remote mode). | |
| GITHUB_APP_ID | No | GitHub App ID used to authenticate with the GitHub API. | |
| GITHUB_WORKSPACE_REPO | No | GitHub repository in the format 'owner/repo' that stores the workspace (for remote mode). | |
| GITHUB_APP_PRIVATE_KEY | No | GitHub App private key content (or path to the key file). | |
| GITHUB_APP_INSTALLATION_ID | No | Installation ID of the GitHub App on the workspace repository. | |
| PERSONAL_CONTEXT_WORKSPACE | No | Path to a local workspace directory containing the context files (for local mode). |
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 |
|---|---|
| context_bootstrapA | Load current personal context for a task. Omit project_hint to read common identity and rules only; use route_hint when a project has multiple task-specific routes. |
| context_closeoutB | Compress a completed, paused, or blocked task into evidence-backed project state and synchronize only files explicitly allowed by the route write policy. |
| context_routesA | List canonical project IDs, exact aliases, task aliases, and route names before choosing project_hint or route_hint. |
| context_queryA | Search the current personal context within explicit scopes and return traceable source excerpts. |
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 targets a distinct phase of context management: bootstrap loads, closeout writes/compresses, routes lists available routes, and query searches. There is no functional overlap or ambiguity about which tool to use.
All tools share the 'context_' prefix, with a brief term following. However, 'routes' is a noun while the others are verbs, creating a slight mismatch, yet the pattern remains predictable and readable.
Four tools is a well-scoped set for a context management server. Each tool earns its place and covers a core operation without unnecessary additions.
The tools cover the full lifecycle: discovering available routes, bootstrapping context, querying during a task, and closing out with state compression. No obvious gaps or dead ends exist for the server's purpose.