Context-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT_MCP_DATA | No | Data directory path | ~/.context-mcp |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| context_addA | Add new context entry to the knowledge base. Use this to remember important decisions, patterns, or information about the project. The entry will be automatically categorized and compressed for efficient retrieval. |
| context_getA | Get the current project context optimized for token efficiency. Returns a hierarchical view:
Use this at the start of conversations to understand the project. |
| context_searchA | Search for specific context in the knowledge base. Use when you need detailed information about a specific topic. Searches across all levels including archived context. |
| context_updateC | Update an existing context entry |
| context_deleteB | Delete a context entry |
| context_relateB | Create a relationship between two context entries for better navigation |
| context_statsB | Get statistics about the context database |
| context_focusA | Set the current work focus. This optimizes which context is loaded. Call this when switching between different areas of the project. |
| context_summarizeA | Generate a compressed summary of recent context. Useful for creating checkpoints or when context is getting too large. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| project_start | Initialize context at the start of a conversation |
| remember_decision | Template for recording an architectural decision |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Core Context | Compressed core context (~500 tokens) - always safe to load |
| Active Context | Current work context (~2000 tokens) |
| Context Statistics | Database statistics and usage |
TDQS
Scored across 9 tools
Each tool targets a distinct action on the context knowledge base: add, get, search, update, delete, relate, stats, focus, and summarize. There is no meaningful overlap; even get and search serve clearly separate purposes (broad optimized view vs. targeted query).
All tool names follow a uniform 'context_' prefix followed by a simple verb (add, get, search, update, delete, relate, stats, focus, summarize). This is a perfect example of consistent verb_noun convention.
With 9 tools, the server is well-scoped. Each tool is meaningful and contributes to the overall context management workflow without redundancy or bloat. This is an ideal size for the stated purpose.
The tool set covers the full lifecycle of context entries: create (add), read (get), update, delete, search, linking (relate), statistics, focus management, and summarization. There are no obvious dead ends or missing core operations.