Most of the surface is upkeep rather than storage: get_analytics separates the memories that keep getting recalled from those that never have, consolidate_memories folds clusters into synthesised facts while archiving the originals with version history, and feedback_memory feeds the ranking back. The heavier tools are model passes rather than lookups — extract_memories, ingest_document, consolidate_memories, generate_skills and extract_principles all run over your content, and get_usage reports extractions this month against a tier, so that work is metered. Rules are the deliberate exception to the ranking: they are injected into every conversation regardless of score or decay.
A hosted memory service behind 37 tools, holding facts, rules, tasks and corrections for a project and returning them to later sessions.
- Recall at session start and at the moment before a suggestion: get_project_context loads the top memories at session start, preflight runs a keyword search before a suggestion is made, and recall_memories runs semantic search filtered by type, category, tag, scope or minimum importance.
- Memories that outrank scoring: save_rule stores a directive injected into every conversation, bypassing scoring and decay, with list_rules and delete_rule to keep the set honest.
- Capture without dictation: extract_memories reads a message-and-response exchange and identifies what is worth keeping, ingest_document chunks a README or API spec into memories, and save_session_summary records what a session settled.
- A safety net over deletion: delete_memory moves an item to the trash where restore_memory and list_trash can recover it for 30 days, and bulk_delete and bulk_update take up to 100 and 50 items per call.
- Structure across memories: link_memories connects two entries with a named relationship, get_memory_links walks the graph, get_memory_versions shows how a fact changed, and list_tags reports the threads in use.
- Upkeep tools that name their own targets: get_analytics reports most-recalled, never-recalled and stale entries, get_stale_memories lists candidates by age, consolidate_memories synthesises clusters of three or more memories sharing a subject, and promote_memory lifts a project fact to global scope.
- Continuity beyond facts: save_task, get_tasks and update_task carry pending and in_progress work across sessions, set_reminder surfaces a note at the next session start, and get_file_changes diffs the repository against the snapshot from last time.
A CogmemAi account and its key in COGMEMAI_API_KEY. get_file_changes compares against git state, so it wants the project under version control.
One command plus a key — npx cogmemai-mcp setup, then supply credentials