
Engram
app.getengramPublished by getengram.appOfficial publisherv0.1.1Updated Oct 24, 2026
Persistent, verbatim, searchable memory for AI assistants — one memory across every MCP client.
Overview
Engram gives an AI assistant persistent, verbatim conversation memory that can be searched semantically across sessions and MCP clients.
- What you can do
- Engram is a remote MCP memory server that stores complete, uncompressed conversation transcripts and makes them searchable by meaning using embeddings. It exposes six tools: create_conversation, append_messages, search, get_conversation, list_conversations and delete_conversation. Memory is shared across connected MCP clients, so an agent can recall earlier sessions. A Claude Code plugin also ships a skill that decides when to search or save memory.
- When to use it
- Use it when you want an assistant to remember past conversations across sessions and across different MCP clients, and to retrieve relevant context by meaning rather than exact keywords. It suits users who accept storing full transcripts in a hosted service.
- Requirements
- A remote endpoint at mcp.getengram.app over streamable HTTP; no local package or API key. OAuth sign-in is required and a free account is created during sign-in. Clients that only support stdio need a bridge such as mcp-remote via npx, which requires Node.js. Network access is required.
Installation
In SourceWeft
- Open Engram in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.getengram%2Fengram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"engram": {
"type": "http",
"url": "https://mcp.getengram.app/mcp"
}
}
}README
Engram
Memory infrastructure for AI agents. Store every conversation verbatim. Search by meaning.
Engram is an MCP-native memory server that stores complete, uncompressed conversation transcripts and makes them searchable via semantic search. Connect any MCP-compatible client — Claude Desktop, Claude Code, Cursor, Windsurf, Zed — and your agent remembers everything across sessions.
Quick start
Claude Code
Restart Claude Code and approve access in the browser. There is no API key to copy and no config file to edit — the server implements the MCP authorization flow (RFC 9728 / 8414 / 7591, PKCE), so the client discovers it, registers itself, and signs you in. A free account is created as part of signing in.
The plugin also ships a skill that tells Claude when to search memory and what is worth saving, so context accumulates without being asked.
Any other MCP client
Point it at the remote server and let OAuth handle access:
For a client that only speaks stdio, bridge to the remote server with mcp-remote — it drives the same browser OAuth flow, so there is still no key to copy:
(An older version of this README suggested npx @getengram/cli mcp; the CLI
has no such command and that configuration never worked.)
How it works
- Verbatim storage — every message stored exactly as sent, no summarization or compression
- Semantic search — find relevant context by meaning using bge-base-en-v1.5 embeddings
- MCP-native — speaks the Model Context Protocol natively, works with any compatible client
- Multi-tenant — per-organization isolation, team seats, and API key management
Architecture
Runs entirely on Cloudflare's developer platform:
- Workers — Hono.js API and MCP server
- D1 — SQLite at the edge for messages and metadata
- Vectorize — semantic search index
- Workers AI — embedding generation
Read the full architecture deep-dive.
MCP tools
Engram exposes 6 tools via MCP:
See the API reference for full parameters and examples.
Packages
Integration guides
Pricing
Memory is permanent. The limits below are how many messages a plan can hold, not a monthly quota: nothing expires, and deleting conversations frees space.
Links
- Website: getengram.app
- Documentation: getengram.app/docs
- Blog: getengram.app/blog
- npm: @getengram/cli
License
Business Source License 1.1 — see LICENSE for details.
Source: README.md at commit accbe3d
Tools
0Version history
2- v0.1.1LatestOct 13, 2026
- v0.1.0Sep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.