iai-personal-memory-engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IAI_MCP_STORE | No | Data directory | ~/.iai-mcp/ |
| IAI_MCP_EMBED_MODEL | No | Embedding model. 'bge-m3' for multilingual at ~3x size. | bge-small-en-v1.5 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_recallA | Recall verbatim memories by cue — decisions, preferences, prior discussion, rationale. Call before a repository search. Returns hits + anti_hits. |
| memory_searchA | Use for code/doc search; returns hints to verify — never replaces a repository search. |
| memory_recall_structuralA | Structural recall via TEM role->filler bindings (BSC hypervectors). Read-only. Prefer over memory_recall for role-filler queries. |
| memory_reinforceA | Boost Hebbian edges among co-retrieved record ids. Mutates edge weights. Use when two records co-answered. |
| memory_contradictA | Mark a record contradicted; new fact stored as a NEW record (old NEVER deleted). Mutates store. |
| memory_captureA | Capture a verbatim turn (auto-dedups near-duplicates). Use for corrections, not for minting standing-order directives. |
| memory_consolidateA | Trigger sleep-cycle consolidation: schema induction, FSRS decay, Hebbian pruning. Mutates store; idempotent in one sleep window. |
| profile_get_setA | Read or write a profile knob (10 sealed: 9 AUTIST + wake_depth). operation get|set; returns knob value. |
| curiosity_pendingA | List pending curiosity questions queued by the sleep daemon. Read-only. Filter by session_id. |
| schema_listA | List induced schemas (Tier-0 + Tier-1) from sleep consolidation. Read-only. Filter by domain and confidence_min. |
| events_queryA | Query user-visible events (kind whitelist). Read-only. Optional since (ISO-8601), severity, limit. |
| topologyA | Snapshot of memory-graph topology: N, C, L, sigma, community_count, regime. Read-only diagnostic; sigma never toggles retrieval. |
| episodes_recentA | Returns the N most-recent user-turn records, time-desc. Optional session_id filter. GLOBAL across all projects. |
| memory_temporal_recallA | Time-travel recall: as_of bounds records, changed_since filters events. Read-only. |
| claim_checkA | Check a claim (e.g. 'X is not done') against memory. Returns hits + anti_hits + a freshness verdict in one call. |
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 15 tools
The set has multiple recall-flavored tools (memory_recall, memory_search, memory_recall_structural, memory_temporal_recall, claim_check), but each description emphasizes a different cue type or output contract. The only notable risk is choosing between memory_recall and memory_temporal_recall for time-bounded verbatim queries, but the descriptions still distinguish them.
Core memory operations use the memory_<verb> pattern consistently, but the convention is mixed across non-core tools: bare nouns (topology), noun_adjective (episodes_recent, curiosity_pending), verb_noun (schema_list, events_query), and verb pairs (profile_get_set). Names are readable individually, but they do not follow a single cohesive convention.
Fifteen tools is at the upper edge of the ideal range, and most operations have a genuine purpose. However, several recall variants and diagnostic read-only tools could potentially be consolidated without making the server less clear.
The memory lifecycle is well covered: capture, recall variants, contradiction, reinforcement, consolidation, profiling, and diagnostics are all present. There is no hard-delete operation, but the descriptions indicate this is intentional (contradicted records are marked, never deleted), so the gap is design-driven rather than accidental.