kiro-total-recall
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kiro-total-recallfind my preference about testing frameworks from past conversations"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kiro Total Recall
Ever told Kiro "like we discussed yesterday" only to realize... it has no idea?
Total Recall gives Kiro the memory it's missing.
The Problem
Sessions Are Isolated: Each Kiro session starts fresh. Yesterday's architecture discussion? Gone.
Projects Don't Share Knowledge: Your preferences (testing style, package managers, patterns) aren't remembered across projects.
CLI and IDE Are Separate: Conversations in Kiro CLI don't connect to Kiro IDE.
Total Recall indexes every Kiro conversation and provides semantic search. Find discussions by meaning, not just keywords.
Related MCP server: claude-kb
Quickstart
As a Kiro Power (Recommended, IDE only)
In Kiro IDE: Powers panel → Add power from GitHub
Enter:
https://github.com/danilop/kiro-total-recallThe power activates automatically when you mention "recall", "remember", or "past conversation"
Manual MCP Setup (CLI and IDE)
Add to ~/.kiro/settings/mcp.json (this config is shared by both CLI and IDE):
{
"mcpServers": {
"total-recall": {
"command": "uvx",
"args": ["--from", "git+https://github.com/danilop/kiro-total-recall", "kiro-total-recall"]
}
}
}Restart Kiro CLI/IDE after adding. MCP servers are only loaded at startup.
Verify Installation
In Kiro CLI: /mcp should list total-recall
In Kiro IDE: Check the MCP Servers panel
How It Works
┌─────────────────────────────────────────────────────────────────────────┐
│ Kiro CLI & IDE │
│ ┌──────────────────────────┐ ┌──────────────────────────────────┐ │
│ │ CLI: SQLite DB │ │ IDE: .chat JSON files │ │
│ │ ~/Library/App Support/ │ │ ~/Library/App Support/Kiro/ │ │
│ │ kiro-cli/data.sqlite3 │ │ User/globalStorage/.../*.chat │ │
│ └────────────┬─────────────┘ └─────────────┬────────────────────┘ │
│ └────────────────┬───────────────┘ │
│ ▼ │
│ ┌───────────────────────┐ │
│ │ Unified Loader │ │
│ └───────────┬───────────┘ │
└────────────────────────────────┼────────────────────────────────────────┘
▼
┌─────────────────────────────────────────────────────────────────────────┐
│ Kiro Total Recall │
│ ┌─────────┐ ┌──────────┐ ┌─────────┐ ┌────────────────────┐ │
│ │ loader │───▶│ indexer │───▶│ query │───▶│ MCP server │ │
│ │ CLI+IDE │ │ 384-dim │ │ cosine │ │ 4 search tools │ │
│ └─────────┘ └────┬─────┘ └─────────┘ └────────────────────┘ │
│ ▼ │
│ ~/.cache/kiro-total-recall/embeddings.pkl │
└─────────────────────────────────────────────────────────────────────────┘The Index: Making Search Fast
On first search, Total Recall:
Loads all messages from CLI (SQLite) and IDE (.chat files)
Embeds each message using all-MiniLM-L6-v2 (384-dimensional vectors)
Caches embeddings to
~/.cache/kiro-total-recall/embeddings.pkl
Subsequent searches are fast because:
Fingerprinting: Only rebuilds when conversations change
Incremental updates: New messages get embedded; existing embeddings loaded from cache
Hash-based deduplication: Same text = same embedding (no recomputation)
Features
Semantic Search: Find by meaning, not just keywords
Dual Source: Searches both CLI and IDE conversations
Context Windows: See surrounding messages for each match
Date Filtering: Filter by time range (ISO 8601)
Incremental Indexing: Only processes new conversations
Memory Limits: Configurable RAM usage (default: 1/3 of RAM)
MCP Tools
Tool | Scope | Use Case |
| Current workspace | Bugs, decisions in this codebase |
| All workspaces | Preferences, patterns across all work |
| CLI only | Kiro CLI conversations |
| IDE only | Kiro IDE conversations |
Parameters
All tools accept:
Parameter | Default | Description |
| required | Keywords or sentence to search |
| none | Filter to messages on/after this date (inclusive). ISO 8601 format. |
| none | Filter to messages before this date (exclusive). ISO 8601 format. |
| 3 | Messages before AND after each match |
| 0.2 | Minimum similarity (0-1, higher = stricter) |
| 10 | Maximum results to return |
| 0 | Skip results (for pagination) |
Date Filtering Examples
# Messages from a specific day
search_project_history(query="auth bug", after="2025-01-15", before="2025-01-16")
# Messages from the past week
search_project_history(query="refactoring", after="2025-01-25")
# Messages in January
search_project_history(query="database", after="2025-01-01", before="2025-02-01")Response Structure
{
"results": [
{
"matched_message": {
"role": "assistant",
"content": "To fix the authentication bug...",
"timestamp": "2025-01-15T10:30:00",
"workspace": "/Users/dev/myproject",
"session_id": "abc123",
"uuid": "msg-456",
"source": "cli"
},
"score": 0.8542,
"context": [
{"role": "user", "content": "How do I fix this auth bug?", "timestamp": "...", "is_match": false},
{"role": "assistant", "content": "To fix the authentication bug...", "timestamp": "...", "is_match": true}
]
}
],
"query": "authentication bug fix",
"total_matches": 25,
"offset": 0,
"has_more": true,
"hint": "Showing 1-10 of 25 matches. Use offset: 10 for more."
}Usage Examples
Just ask naturally:
"How did we fix that auth bug?"
"What did we discuss about the database schema?"
"What's my usual approach to error handling?"
"Find our React component discussions from last week"Or use tools directly:
search_project_history(query="authentication bug fix")
search_global_history(query="React component patterns")
search_cli_history(query="deployment", after="2025-01-01")Configuration
Create ~/.config/kiro-total-recall/config.toml to customize:
[sources.cli]
enabled = true
paths = [
"~/Library/Application Support/kiro-cli/data.sqlite3",
"~/.local/share/kiro-cli/data.sqlite3",
"~/AppData/Roaming/kiro-cli/data.sqlite3",
]
[sources.ide]
enabled = true
patterns = [
"~/Library/Application Support/Kiro/User/globalStorage/kiro.kiroagent/*/*.chat",
"~/.config/Kiro/User/globalStorage/kiro.kiroagent/*/*.chat",
"~/AppData/Roaming/Kiro/User/globalStorage/kiro.kiroagent/*/*.chat",
]
[embedding]
model = "all-MiniLM-L6-v2"
cache_dir = "~/.cache/kiro-total-recall"
[search]
default_threshold = 0.2
default_max_results = 10
default_context_window = 3
[memory]
fraction = 0.33 # Use 1/3 of RAM
# limit_mb = 512 # Or set explicit limitMemory Management
Total Recall limits in-memory index size to prevent excessive memory usage. By default, it uses 1/3 of physical RAM. When the limit is reached, the oldest sessions are excluded from the index (newest sessions are kept).
Variable | Description | Default |
| Override memory limit in MB | 1/3 of RAM |
| Set to any value to disable limit | - |
Testing
# Test server starts
uvx kiro-total-recall
# Ctrl+C to exit
# Test search directly
uv run python -c "
from kiro_total_recall.query import search_conversations
result = search_conversations(query='bug fix', max_results=3)
print(f'Found {result.total_matches} matches')
"Project Structure
kiro-total-recall/
├── POWER.md # Kiro Power manifest + steering
├── mcp.json # MCP server config for Power
├── config.default.toml # Default configuration
├── src/kiro_total_recall/
│ ├── server.py # FastMCP server, tool definitions
│ ├── query.py # Search engine, deduplication
│ ├── indexer.py # Embedding, caching, fingerprinting
│ ├── loader.py # Unified loader (CLI + IDE)
│ ├── cli_loader.py # SQLite parsing for CLI
│ ├── ide_loader.py # JSON parsing for IDE .chat files
│ ├── config.py # Configuration management
│ └── models.py # Pydantic data models
├── pyproject.toml
└── LICENSETechnical Details
Component | Technology |
Embedding model | all-MiniLM-L6-v2 (384 dimensions) |
Vector search | Cosine similarity via NumPy dot product |
Cache format | Python pickle with file locking |
MCP framework | |
Package manager |
License
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danilop/kiro-total-recall'
If you have feedback or need assistance with the MCP directory API, please join our Discord server