The Context-Saver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CS_CONFIG | No | Path to the servers.json configuration file. Search order is --config <path>, CS_CONFIG, ~/.context-saver/servers.json, then ./servers.json. | |
| CS_API_KEY | No | API key used when running remote mode with apikey authentication; checked in constant time. | |
| CS_PUBLIC_URL | No | Public URL of the server, used for OAuth mode behind TLS. | |
| CS_ACCESS_CODE | No | Access code for the OAuth popup login page when running remote mode with OAuth authentication. | |
| CS_TOKEN_SECRET | No | Secret used to sign OAuth tokens in OAuth authentication 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 |
|---|---|
| list_serversA | List the upstream MCP servers multiplexed by this gateway, with health, circuit-breaker state and tool counts. Cheap: call this first to orient yourself. |
| list_toolsA | List upstream tools COMPACTLY (name + one-line description, no JSON schemas). Optionally filter to one server. Set refresh=true to force a live re-index. |
| search_toolsA | Search every upstream tool by keywords. Returns ranked matches with reasons and per-tool schema cost. Schemas are NOT included — load the ones you need with get_tool_schema. |
| suggest_toolsA | THE core trick: pass the user's current prompt. Ranks the catalog against it and returns the best-matching upstream tools WITH their full JSON schemas in this single response — so one cheap call replaces loading every schema. Default top_k=4 keeps context lean; raise it for complex multi-tool tasks. |
| get_tool_schemaA | Fetch the complete JSON schema (and annotations) of exactly ONE upstream tool — the precise, lazy-loading primitive. Prefer suggest_tools when you only have a vague prompt; call this when you already know the tool. |
| call_toolA | Run a tool on an upstream MCP server. Arguments are passed through unmodified and validated by the upstream against the schema you loaded. Timeouts, one automatic reconnect, and a circuit breaker protect your turn from stuck upstreams. |
| gateway_statusA | Health of every upstream (status, latency, error counts, breaker state) plus the context-savings report: tokens a direct connection would burn vs. tokens this session actually spent. |
| reload_configA | Re-read servers.json and apply changes WITHOUT restarting the gateway: new servers appear, removed ones are disconnected, unchanged ones keep their connections. Fails safely — a broken config leaves the current setup running. |
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 8 tools
The tools are mostly distinct: discovery is split into list_tools (compact list), search_tools (keyword search), suggest_tools (prompt-ranked with schemas), and get_tool_schema (single schema load), with clear boundaries. The main overlap is list_servers vs gateway_status, both of which expose upstream health/circuit-breaker state, though the descriptions differentiate cheap orientation from detailed status reporting.
All names use snake_case and most follow a predictable verb_object pattern: list_servers, list_tools, search_tools, suggest_tools, get_tool_schema, call_tool, reload_config. gateway_status is the one noun-phrase outlier, a minor deviation rather than a pattern break.
Eight tools is well-scoped for a gateway that needs to orient, discover, load schemas, invoke upstream tools, report health, and reload config. Each tool has a clear role in the workflow, and there is no obvious padding.
The surface covers the core gateway lifecycle: list servers/tools, search and suggest tools, fetch schemas, call upstream tools, report status, and reload configuration. Minor gaps remain around explicit server connection management, circuit-breaker reset, or MCP resources/prompts if those upstream capabilities are in scope.