Slipstream - Built by Vektor Memory - a persistent multi-layered memory architecture. 4-layer associative graph memory (MAGMA) with autonomous REM cycle, CLI, DXT-MCP Cloak Tools.
Hand a project over — to your next session, to Cursor/Codex/Gemini, to your successor — with the reasons attached. Local-first memory MCP for coding agents: decisions re-injected before the agent acts, drift detection across every project you run. One SQLite file, nothing leaves your machine.
Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.
Exposes tools that let an agent search a local Markdown-based memory store, fetch full cards by id, write new knowledge cards that are indexed immediately, and inspect or rebuild the SQLite index. All retrieval runs locally over Chinese-friendly full-text search with graded exact/prefix matching, so agents without a memory system can recall prior notes while existing Markdown files stay read-only.
MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others.
The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.
Enables AI assistants to save resolved debugging sessions as concise experience cards into a local JSON knowledge network, and to retrieve relevant past cards when new bugs arise. It also powers a spaced-repetition review interface to reinforce memory of those experiences.
Gives AI coding agents persistent, evolving knowledge about a codebase, enabling them to store and retrieve observations about architecture, conventions, gotchas, and recent work context.
A different approach from typical persistent-memory MCPs. Instead of a local
SQLite + embeddings store, the memory lives as plain files in a .ai-memory/
directory you commit to your repo (facts.jsonl, decisions/\*.md, gotchas.md).
Git is the sync layer — what one Claude/Cursor/Cline learns about a repo, the
next session (or a teammate's agent) picks up automatically.
5 MCP tools: get_rep
Persistent knowledge graph MCP server with SQLite backend, offering graph traversal, fuzzy search, and temporal queries for entities and relations. It serves as a drop-in replacement for the npm mcp-server-memory with enhanced capabilities.
An MCP server that implements memory with decay mechanics, allowing AI agents to store and retrieve memories that fade over time unless accessed, with a permanent journal for verification.
Automatically records AI conversation turns and code changes to local Markdown files to provide persistent context across chat sessions. It enables AI agents to search history through MCP tools and provides a web viewer for browsing past discussions.
Enables coding agents to query and modify a SQLite database through twelve SQL-based tools, with safety enforced server-side via statement policies, protected tables, result caps, and snapshots. It also provides an append-only, hash-chained memory log with checkpoints so agents can record events and resume context across sessions.