kiro-total-recall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIRO_RECALL_MEMORY_LIMIT_MB | No | Override memory limit in MB. Default is 1/3 of RAM. | |
| KIRO_RECALL_NO_MEMORY_LIMIT | No | Set to any value to disable memory limit. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
| 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 |
| search_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 |
| 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.