A
licenseNot graded
qualityB
maintenanceStructured, versioned context for AI agents. Context Nest organizes knowledge as markdown documents in a vault, with versioning, integrity verification, and a query language.
20
AGPL 3.0
Context Forge
by Radics
Related Servers
Alternatives to Context Forge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA context preservation engine for AI agents that bundles project state into a markdown package and syncs it to clipboard or cloud, enabling zero knowledge loss across sessions.28 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to store and retrieve project-aware context as plain Markdown files locally, with no cloud or vector database required.2MIT
- AlicenseAqualityDmaintenanceEnables AI coding agents to persist structured long-term memory (gotchas, architecture, API notes) in a .context folder and sync across devices and agents via Git.47 npm20MIT
- AlicenseAqualityAmaintenanceOne context engine for every AI. Persistent context from GitHub, Notion, and your decisions, delivered to Claude, ChatGPT, Cursor, VS Code, Gemini, and any MCP-compatible client.93AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to retain and recall project context across sessions through local Markdown storage and hybrid keyword/semantic retrieval, including reusable knowledge cards. It runs offline as a daemon and integrates with MCP-compatible IDEs to continue long-running work without re-explaining decisions or architecture.47 npm12MIT
TDQS
A3.5/5.0
Scored across 7 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityStale
ResponsivenessNo issues