Engram Rs
@kael-bit
About Engram Rs
Hierarchical memory for AI agents. Three-layer (buffer/working/core) with automatic decay, promotion, and semantic search.
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"engram": {
"command": "npx",
"args": [
"-y",
"engram-rs-mcp"
],
"env": {
"ENGRAM_URL": "http://localhost:3917",
"ENGRAM_API_KEY": "",
"ENGRAM_NAMESPACE": ""
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Engram Rs?
Engram Rs is a Model Context Protocol (MCP) server that gives AI agents persistent, human-like memory. It organizes memories through three cognitive layers — buffer (short-term), working (active knowledge), and core (long-term) — with automatic decay, promotion, and consolidation. Built as a local-first, single-binary Rust server using SQLite, it is designed for developers adding long-term memory to MCP-compatible AI clients.
How to use Engram Rs?
Download the platform-specific Rust binary and run it with any MCP client that supports stdio transport, such as Claude Desktop, Cursor, or Windsurf. The server exposes tools for storing, searching, deduplicating, and managing memories across isolated namespaces, and it can extract session context from LLM conversations.
Key features of Engram Rs
- Three-tier memory: buffer, working, and core layers
- Semantic search via HNSW vector index
- Automatic deduplication and merging of memories
- Namespace isolation for multi-agent setups
- Session context extraction from LLM conversations
- Local-first, single-binary Rust server with SQLite
Use cases of Engram Rs
- Give conversational AI agents persistent, long-term memory across sessions
- Manage multiple agent identities with isolated memory namespaces
- Extract and consolidate key information from ongoing LLM conversations
- Maintain context and knowledge without relying on proprietary cloud services
FAQ from Engram Rs
What makes Engram Rs different from other memory systems?
It uses a three-layer cognitive architecture with automatic decay, promotion, and consolidation, mimicking human memory dynamics rather than a flat storage approach.
What runtime or dependencies are required?
None beyond the compiled Rust binary. It is a local-first, single‑binary server that uses SQLite – no external databases, cloud services, or additional runtimes needed.
Where are memories stored?
All memories are stored locally in an SQLite database managed by the Rust server. No data is sent to external services.
What transport and authentication does it use?
It uses the MCP protocol over stdio transport. Authentication is not covered in the README.
What clients does Engram Rs work with?
It works with Claude Desktop, Cursor, Windsurf, and any MCP‑compatible client that supports stdio transport.
More Memory & Knowledge MCP servers
Solomd
zhitongblogA markdown editor — and the bridge to your LLM. Local-first, MIT, ~15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.
Rust Docs MCP Server
Govcraft🦀 Prevents outdated Rust code suggestions from AI assistants. This MCP server fetches current crate docs, uses embeddings/LLMs, and provides accurate context via a tool call.
Obsidian MCP Server
cyanheadsRead, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.
Dash Api Docs Mcp Server
KapeliMCP server for Dash, the macOS API documentation browser
RAG Documentation MCP Server
hannesrudolphAn MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.
Comments