mcp-context-monitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT_MONITOR_BPT | No | Bytes-per-token ratio | |
| CONTEXT_MONITOR_BUFFER | No | Autocompact buffer (tokens) | |
| CONTEXT_MONITOR_WINDOW | No | Context window size (tokens) | |
| CONTEXT_MONITOR_BACKEND | No | Force backend: claude-code or codex-cli | |
| CONTEXT_MONITOR_OVERHEAD | No | Static overhead estimate (tokens) | |
| CONTEXT_MONITOR_TRANSCRIPT | No | Explicit transcript file path | |
| CONTEXT_MONITOR_PROJECT_DIR | No | Transcript directory |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| context_statusA | Estimate current context window usage and distance to compaction. Returns phase (open/midstream/narrowing/threshold), token estimates, and profile range (coding/balanced/reading). Use this to self-manage: open (<50%), midstream (50-80%), narrowing (80-92%, start choosing what to carry), threshold (>92%, write what matters now). Optionally pass transcript_path to target a specific session file. |
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 a single tool, there is no ambiguity or overlap in the set. The tool's purpose is clearly defined and distinct.
The tool name 'context_status' is descriptive and follows a consistent style. Since there is only one tool, naming consistency is perfect.
The server has exactly one tool, which is considered too few for a functional toolset. It provides a single point of functionality but lacks supporting tools.
The tool covers the core need of monitoring context usage with clear thresholds, but it lacks additional features like history tracking or configuration, leaving minor gaps.