kiro-total-recall
Click on "Deploy 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-recall find 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
Available Tools
4 toolssearch_cli_historyA
Search Kiro CLI conversation history only.
Use this to find conversations from Kiro CLI sessions specifically.
Args: query: Keywords or sentence describing what to find after: Filter to messages on/after this date (ISO 8601) before: Filter to messages before this date (ISO 8601) context_size: Messages before AND after each match (default: 3) threshold: Minimum similarity 0-1 (default: 0.2) max_results: Maximum results (default: 10) offset: Skip results for pagination (default: 0)
Returns: Search results from CLI conversations only
Inputs: query (required), after, before, offset, +3 more.
search_global_historyA
Search conversation history across ALL WORKSPACES.
Use this to find cross-project knowledge: user preferences, coding patterns, common solutions, and insights from all previous work.
Args: query: Keywords or sentence describing what to find after: Filter to messages on/after this date (ISO 8601: "2025-01-15") before: Filter to messages before this date (ISO 8601) context_size: Messages to include before AND after each match (default: 3) threshold: Minimum similarity 0-1 (default: 0.2) max_results: Maximum results to return (default: 10) offset: Skip results for pagination (default: 0)
Returns: Search results with matched messages, scores, workspace, context, pagination
Inputs: query (required), after, before, offset, +3 more.
search_ide_historyA
Search Kiro IDE conversation history only.
Use this to find conversations from Kiro IDE sessions specifically.
Args: query: Keywords or sentence describing what to find after: Filter to messages on/after this date (ISO 8601) before: Filter to messages before this date (ISO 8601) context_size: Messages before AND after each match (default: 3) threshold: Minimum similarity 0-1 (default: 0.2) max_results: Maximum results (default: 10) offset: Skip results for pagination (default: 0)
Returns: Search results from IDE conversations only
Inputs: query (required), after, before, offset, +3 more.
search_project_historyA
Search conversation history for the CURRENT WORKSPACE only.
Use this to find workspace-specific context: past decisions, implementation details, bugs discussed, architecture choices in this codebase.
Args: query: Keywords or sentence describing what to find after: Filter to messages on/after this date (ISO 8601: "2025-01-15") before: Filter to messages before this date (ISO 8601) context_size: Messages to include before AND after each match (default: 3) threshold: Minimum similarity 0-1 (default: 0.2) max_results: Maximum results to return (default: 10) offset: Skip results for pagination (default: 0)
Returns: Search results with matched messages, scores, context, and pagination info
Inputs: query (required), after, before, offset, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct scope (CLI, IDE, current workspace, all workspaces) with clear descriptions, leaving no ambiguity about which to use.
All tools follow a consistent verb_noun pattern (search_*_history) with snake_case, making the naming predictable and easy to understand.
With 4 tools, the set is well-scoped for searching conversation history across different contexts; not too few or too many.
The tools cover all relevant search scopes (CLI, IDE, workspace, global) and include necessary parameters like date filters, pagination, and similarity threshold, leaving no obvious gaps.
Related MCP Connectors
Persistent memory for AI assistants: store, search, and connect knowledge across conversations.
Persistent memory for AI agents. Search, store, and recall across sessions.
Universal persistent memory and knowledge retrieval layer for AI agents and LLMs.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI to automatically search, retrieve, and organize your Cursor chat history across sessions. Supports tagging, nicknames, project-scoped search, and full-text search to maintain context between conversations.-
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Claude Code conversation history via hybrid semantic and keyword search, allowing the agent to access its own past interactions.71 PyPI5MIT
- AlicenseAqualityDmaintenanceEnables Claude Code to search, browse, and read its own past conversation history across all projects using BM25 keyword search.18 npmMIT
- AlicenseBqualityCmaintenanceProvides local, agentic semantic recall over Claude Code session history, enabling the agent to search past discussions semantically, expand turns, and grep transcripts.513MIT