ContextKeeper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_context_itemsB | List all context items from ContextKeeper. Shows ID, content, project, tags, and completion status. |
| add_context_itemA | Add a new context item to ContextKeeper. Use this to track tasks, ideas, or notes. |
| mark_context_doneA | Mark a context item as completed using its ID (full UUID or 6-char prefix). |
| get_context_statusA | Get a summary of the context: total items, completed vs active counts, projects, and tags. |
| search_context_itemsA | Search context items by query string and/or tags. Returns matching items with their details. |
| remove_context_itemA | Remove (archive) a context item by ID. The item is soft-deleted and can be recovered. |
| edit_context_itemB | Edit an existing context item's content and/or tags using its ID. |
| sync_context_itemsB | Trigger a sync of context items to AI agent files. Updates the .context-keeper directory. |
| init_contextA | Initialize a new ContextKeeper directory with .contextkeeper folder and items.json 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 9 tools
Each tool has a clearly distinct purpose: list vs search vs status, CRUD operations (add, edit, mark_done, remove), and setup/sync (init, sync). No two tools could be easily confused.
All tools follow a consistent snake_case verb_noun pattern: list_context_items, add_context_item, mark_context_done, get_context_status, search_context_items, remove_context_item, edit_context_item, sync_context_items, init_context.
9 tools is well-scoped for a context management server, covering all essential operations without redundancy or bloat.
Core CRUD and lifecycle are covered (create, read, update, delete, status, search, sync). Minor gap: soft-deleted items are described as recoverable but no explicit recovery tool is exposed, which is a small dead end.