Kilonova MCP
Related Servers
Alternatives to Kilonova MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides Claude with persistent, semantic knowledge of a codebase across sessions by maintaining a local knowledge base of structural maps, compressed file summaries, and insights.7 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.23 npm4MIT
- FlicenseNot gradedqualityDmaintenanceProvides persistent semantic memory for Claude Code via local embeddings and six MCP tools, enabling context storage and retrieval across sessions without cloud dependencies.-
- AlicenseNot gradedqualityCmaintenancePersistent project memory + architectural decisions + pre-execution safety hooks for Claude Code. Local-only storage, multi-repo workspace, automatic knowledge extraction via background auditor.8 npm14MIT
- AlicenseBqualityDmaintenancePersistent, searchable project memory for Claude Code. Each project has its own local DuckDB with vector embeddings, auto-loading context at session start.2432MIT
- AlicenseAqualityDmaintenancePersistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.437MIT
TDQS
Scored across 8 tools
The core CRUD/search set (kb_search, kb_load, kb_write, kb_schema) is clearly differentiated by verb. The main soft overlap is between kb_topics (lists topics with entity type counts) and corpus_status (record counts, size, last modified), which could be confused by an agent wanting topic-level metrics; kb_load vs dot_load is also close but distinguished by entity record vs whole-document.
Six of eight tools use a clean prefix_resource pattern (kb_topics, kb_search, kb_load, kb_write, kb_schema, kb_backup), and dot_load is readable in context. corpus_status breaks the naming family by dropping the kb_ prefix, which is a minor but noticeable deviation.
Eight tools is well within the sweet spot and each maps to a distinct need: discovery, search, load, write, schema, full-document load, status, and backup. Nothing feels padded or redundant.
The surface covers discovery, search, read, write/update, schema introspection, bulk-document load, and backup, which is solid lifecycle coverage for a knowledge base. The visible gap is deletion/removal of entity records — kb_write can create and overwrite, but there is no way to delete an obsolete record.