Krusch Context MCP
Related Servers
Alternatives to Krusch Context MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to store decisions, preferences, and lessons in a local SQLite store, then recall the most relevant ones on demand. Runs fully local — no cloud, API keys, or per-query cost — and also exposes forget and consolidate operations.2Apache 2.0
- AlicenseAqualityBmaintenancePersistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.224MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and recall persistent project-specific and cross-project context — decisions, preferences, error patterns, and guidelines — from a local-first SQLite memory store with semantic search, so knowledge survives across sessions. An optional companion task server lets agents queue and autonomously execute work using that same memory.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent local memory during sessions, storing and semantically searching project decisions, preferences, error patterns, guidelines, and cross-project standards from SQLite stores on the user's machine. An optional companion server also exposes an autonomous task queue for executing queued work.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent memory directly during sessions, storing decisions, preferences, error patterns, research, and cross-project guidelines in local SQLite databases. Supports semantic search so relevant project and global context can be recalled by meaning, fully offline and without API keys.-
- FlicenseNot gradedqualityAmaintenanceGives AI coding agents direct, local-first read/write access to persistent memory — project decisions, preferences, error patterns, research, and cross-project guidelines — retrieved by semantic search backed by SQLite with no API keys or network calls. A companion server also exposes optional autonomous task-queue execution.-
TDQS
Scored across 5 tools
Retrieve (read), remember (write new), nudge (audit), and health (ops) are clearly distinct. The only soft boundary is remember vs revise, since both mutate knowledge, but descriptions differentiate creating new memories from superseding/invalidating existing ones.
All tools share a consistent krusch_context_* namespace with a single descriptive suffix, making the set predictable. Minor deviation: retrieve/remember/revise/nudge are verbs but health is a noun, breaking the verb-based pattern slightly.
Five tools is well-scoped for a context/memory server: one per lifecycle concern (read, write, revise, audit, health). Each tool earns its place with no redundancy or bloat.
The surface covers the core memory lifecycle: retrieval, creation with dedup, temporal revision/invalidation, invariant auditing, and health inspection. Minor gaps remain, such as an explicit forget/delete operation or a targeted memory search/listing tool.