Context Forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXTFORGE_WEBDAV_URL | No | The URL of the WebDAV server for synchronization. | |
| CONTEXTFORGE_WEBDAV_PASSWORD | No | The password for WebDAV authentication. | |
| CONTEXTFORGE_WEBDAV_USERNAME | No | The username for WebDAV authentication. |
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 |
|---|---|
| get_contextA | Get task-scoped project context within a token budget. |
| search_contextA | Search portable context, optionally within one project. |
| get_runbookB | Get a project runbook by operation key. |
| write_handoffB | Write a structured, evidence-backed handoff for another agent. |
| checkpoint_statusA | Show the pending handoff window and automatic checkpoint trigger state. |
| record_factC | Record a project fact with evidence and confidence. |
| sync_statusB | Show local cache and synchronization status. |
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 7 tools
Tools are mostly distinct: get_context and search_context both retrieve context but are differentiated by task-scoping vs. searching. checkpoint_status and sync_status are both status checks but cover different system aspects, so ambiguity is low overall.
Most tools follow a clear verb_noun pattern (get_context, write_handoff, record_fact). checkpoint_status and sync_status deviate slightly as they are noun-like status queries, but the naming remains consistent in style and predictable.
With 7 tools, the server is well-scoped for its purpose of context and handoff management. Each tool covers a distinct functional area, and the count is neither sparse nor bloated.
The tool set covers core operations: retrieving context, searching, getting runbooks, writing handoffs, recording facts, and checking status. Minor gaps include no update or delete operations for facts or contexts, but the primary lifecycle for the domain appears covered.