Kilonova MCP
Persistent knowledge base tools for Claude Code that store project context, decisions, and patterns locally across sessions, eliminating cold starts.
README
Kilonova MCP
Persistent knowledge base tools for Claude Code.
Claude remembers your projects, decisions, and patterns across sessions — stored on your machine, no cloud required.
Built by AIM Studio · Free · MIT License
The Problem
Every Claude Code session starts cold. You re-explain your project structure, re-describe decisions you made last week, re-state what's in flight. Context burns fast.
The Solution: DOT + KB
Kilonova gives Claude a persistent knowledge base on your local machine. At session start, Claude loads your DOT (Document of Truth) — a compressed, structured reference doc with your project state, active tasks, decisions, and patterns. During the session, Claude writes new discoveries back to the KB. Next session, it's all there.
Session 1: Claude learns your architecture → kb_write saves the decision
Session 2: dot_load → Claude already knows. No recap needed.
Install
pip install kilonova-mcp
Or from source:
git clone https://github.com/MilnaOS/kilonova-mcp
cd kilonova-mcp
pip install -e .
Wire Up Claude Code
Add to ~/.claude/settings.json:
{
"mcpServers": {
"kilonova": {
"command": "python",
"args": ["-m", "kilonova_mcp"],
"env": {
"KILONOVA_KB_ROOT": "/path/to/your/kb"
}
}
}
}
Copy CLAUDE.md.template to ~/.claude/CLAUDE.md (or append to your existing one).
Quick Start
1. Create your first KB topic:
In Claude Code, just start writing:
mcp__kilonova__kb_write(
topic="claude_context",
entity_type="project_state",
name="my-project",
data={
"name": "my-project",
"status": "active",
"location": "/path/to/project",
"summary": "What this project is",
"next_action": "What to do next"
}
)
2. Load it next session:
mcp__kilonova__dot_load(topic="claude_context")
3. Search it:
mcp__kilonova__kb_search(topic="claude_context", query="authentication decision")
The DOT Format
A DOT is a plain text file with three sections:
---SYMBOLS---
[PR]=My Project (/path/to/project)
[DB]=Database (PostgreSQL on localhost:5432)
---TOC---
1:Projects|1.1:My_Project
2:Active_Tasks
3:Decisions
---CARDS---
## [1] PROJECTS
### [1.1] My Project
STATUS: active
NEXT: wire up the auth flow
Symbols compress repeated references. The TOC lets Claude fetch only the section it needs. Cards hold the actual content.
See example_dot/ for a starter template.
Starter Schema: claude_context
Copy schemas/claude_context/ into your KB directory under <kb_root>/claude_context/schemas/:
| Entity type | Use for |
|---|---|
project_state |
Current status, location, next action per project |
decision |
Architectural choices with rationale |
pattern |
Code conventions, gotchas, file locations |
active_task |
In-flight work across sessions |
session_note |
End-of-session summaries |
Tools
| Tool | Description |
|---|---|
dot_load(topic) |
Load full DOT document into context |
kb_search(topic, query) |
Search records by natural language query |
kb_write(topic, entity_type, name, data) |
Write/update a record (merges with existing) |
kb_load(topic, entity_type, name) |
Load one specific record |
kb_topics() |
List all KB topics and record counts |
kb_schema(topic, entity_type?) |
Show field schema for an entity type |
corpus_status(topic) |
Show KB size and record counts |
kb_backup(dry?) |
Mirror KB to OneDrive |
Bring Your Own KB
Kilonova doesn't care what you store. Define your own schemas:
// kb/my_topic/schemas/component.json
{
"name": {"type": "string", "description": "Component name"},
"file": {"type": "string", "description": "Path to file"},
"purpose": {"type": "string", "description": "What it does"},
"dependencies": {"type": "array", "description": "What it depends on"}
}
Then write records to it and search them naturally.
Part of the Kilonova Ecosystem
Kilonova MCP is the free, standalone KB layer extracted from Milna OS — a full BYOK multi-model AI terminal. If you want the whole thing (parallel model legs, distillation engine, web ingestion, local+cloud hybrid inference), check out Milna OS.
MIT License · © AIM Studio
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。