kiro-recall
A local MCP memory server for Kiro CLI that provides persistent semantic memory across sessions using SQLite for storage, Ollama for local vector embeddings, and Obsidian as a human-readable sync target.
README
kiro-recall
A local MCP memory server for Kiro CLI that gives your AI assistant persistent, semantic memory across sessions.
Inspired by Kiro Crew's memory architecture — reimplemented as a lightweight, self-contained system using SQLite + Ollama embeddings, with Obsidian as the human-readable sync target.
What it does
- Semantic memory — structured key-value facts (
pref.editor: Neovim,project.active: MyProject) - Episodic memory — conversation fragments that decay over time (~23 day half-life)
- Lessons — corrections and rules that override all other memory (highest priority)
- Semantic recall — vector similarity search via Qwen3-Embedding (1024-dim, runs locally)
- Obsidian sync — renders memory to markdown with
[[wikilinks]]for graph navigation
Architecture
┌──────────────────────────────────────────┐
│ Kiro CLI / any MCP client │
│ Tools: Remember, Recall, Learn, Forget │
└──────────────┬───────────────────────────┘
│ stdio (MCP protocol)
┌───────▼───────┐ ┌─────────────────┐
│ memory.db │ sync → │ Obsidian Vault │
│ (SQLite) │ │ (Markdown) │
└───────┬───────┘ └─────────────────┘
│
┌───────▼───────┐
│ Ollama │
│ qwen3-embed │
│ (localhost) │
└───────────────┘
Requirements
Install
git clone https://github.com/fredluckham/kiro-recall.git
cd kiro-recall
bash install.sh
The install script will:
- Install Ollama (if not present) and start it as a service
- Pull the
qwen3-embedding:0.6bmodel - Create a Python venv and install dependencies
- Install the MCP server config into
~/.kiro/settings/mcp.json - Install the steering file to
~/.kiro/steering/obsidian-memory.md - Optionally seed memory from an existing Obsidian vault
Manual setup
If you prefer not to use the install script:#
# 1. Install Ollama and the embedding model
brew install ollama # or: curl -fsSL https://ollama.com/install.sh | sh
brew services start ollama
ollama pull qwen3-embedding:0.6b
# 2. Create venv and install deps
uv venv .venv
uv pip install "mcp[cli]>=1.0.0" "httpx>=0.27.0"
# 3. Copy to ~/.kiro/recall
mkdir -p ~/.kiro/recall
cp server.py db.py embed.py obsidian_sync.py ~/.kiro/recall/
# 4. Add to MCP config (see install.sh for the JSON patch)
MCP Tools
| Tool | Description |
|---|---|
Remember |
Store a fact, episode, or lesson |
Recall |
Semantic search across all memory |
Learn |
Store a high-priority correction/rule |
Forget |
Remove a memory by key or ID |
MemoryStats |
Show counts, age, and decay health per memory tier |
PruneMemory |
Hard-delete soft-deleted and fully decayed episodic rows |
Memory tiers
| Tier | Priority | Decay | Use case |
|---|---|---|---|
| Lessons | Highest | None | "Always use wikilinks", "Never assume region" |
| Semantic | High | None (updated in place) | Structured facts about user/projects |
| Episodic | Medium | exp(-0.03 × days) | Conversation fragments, decisions |
Key format
pref.*— User preferences (pref.theme,pref.voice,pref.editor)project.*— Active projects (project.active,project.stack)user.*— User facts (user.role,user.company,user.tools)
Obsidian sync
Run manually or via cron:
~/.kiro/recall/.venv/bin/python ~/.kiro/recall/obsidian_sync.py
Outputs:
Memory/Semantic.md— all facts grouped by prefixMemory/Lessons.md— corrections grouped by categorySessions/YYYY-MM-DD.md— today's episodic memories
Configuration
Set the Obsidian vault path via environment variable (prompted during install, saved to ~/.kiro/recall/.env):
export KIRO_MEMORY_VAULT="$HOME/Documents/Obsidian/My Vault"
The default is ~/Documents/Obsidian/Kiro Knowledge Base.
Enable automatic Obsidian sync after every Remember or Learn call:
export KIRO_MEMORY_AUTOSYNC=1
When disabled (default), sync runs manually or via cron. Auto-sync adds a small write overhead per call but keeps the vault always current.
The Ollama endpoint is set in embed.py:
OLLAMA_URL = "http://localhost:11434/api/embed"
MODEL = "qwen3-embedding:0.6b"
License
MIT
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。