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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.