Kilonova MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KILONOVA_KB_ROOT | Yes | Path to the knowledge base directory |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kb_searchA | Search a Kilonova knowledge base for records matching a query. Pass topic="claude_context" to search your session notes, decisions, and project state. Pass any other topic name for domain-specific KBs (game systems, research, codebases, etc.). |
| kb_loadC | Load a specific entity record from a KB by name. |
| kb_writeA | Write or update an entity record in a KB. Use this mid-session to persist decisions, task state, patterns, or any structured note. Merges with existing record — only non-empty fields overwrite. |
| kb_topicsA | List all available KB topics and their entity type counts. |
| kb_schemaA | Show field schema for an entity type in a KB topic. Call with no entity_type to list all schema types for the topic. |
| dot_loadA | Load the full DOT (Document of Truth) for a KB topic. A DOT is a compressed, structured reference document with a TOC and cards. Use dot_load("claude_context") at session start to load your persistent working memory. |
| corpus_statusA | Show ingestion progress for a topic — record counts, file size, last modified. |
| kb_backupB | Mirror the KB folder to OneDrive. Use dry=true to preview without copying. |
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 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.