Login

Integration

Long-term memory for Claude Code

Claude Code sessions don't share state. Open the same repo tomorrow morning and you're back to explaining the architecture, your conventions, and last week's decisions from scratch. The plugin marketplace handles install; memory across sessions is what makes the experience feel native.

Get an API key (free) All integrations →

Install

Three steps: sign up for an Engram API key, paste a BYOK LLM-provider key on /models, then drop the snippet below into Claude Code.

Three steps to memory in your agent

  1. Sign up. Free, no card. You'll land on a Getting Started page that walks the next two steps.
  2. Add your LLM key. Engram is BYOK. Paste an OpenAI / Anthropic / Groq / Together / Fireworks key and we'll route every extraction and query call through your provider. You pay your provider directly. We never see your inference.
  3. Paste the snippet below into your agent and restart it. Use Authorization: Bearer <api-key>with the API key from your portal.

Two ways to install; pick one.

Option A: Plugin marketplace (recommended)

One-line install. Adds the Engram MCP server plus /engram-remember and /engram-recall slash commands. No JSON file editing.

  1. Add the Lumetra marketplace:
    2. Claude Code
    /plugin marketplace add lumetra-io/engram-claude-plugin
  2. Install the plugin:
    3. Claude Code
    /plugin install engram@lumetra
  3. Paste your API key when prompted. The plugin stores it in Claude Code's secret store and wires the MCP server automatically.
or

Option B: Manual CLI install

Skips the slash commands but wires the MCP server directly. Includes the required Authorization header.

  1. Add via CLI:
    2. Terminal
    claude mcp add-json engram '{"type":"sse","url":"https://mcp.lumetra.io/mcp/sse","headers":{"Authorization":"Bearer <api-key>"}}'
  2. Restart Claude Code and verify the server is connected.

What you can do once memory's wired in

  • Remember the migration plan we agreed on for the Postgres to DynamoDB cutover
  • Recall which libraries you've already evaluated and rejected for this project, and why
  • Pull up the API contract we settled on between the frontend and the auth service
  • Keep your preferred test framework, formatter, and naming style consistent across sessions

FAQ

What's the full install sequence?

Two steps in Claude Code: `/plugin marketplace add lumetra-io/engram-claude-plugin` to register Lumetra's marketplace, then `/plugin install engram@lumetra` to install. The slash commands are then available in every workspace.

Where does Claude Code store my Engram API key?

The plugin uses Claude Code's `user_config` mechanism. You're prompted for `ENGRAM_API_KEY` on install, Claude Code stores it, and the plugin manifest references it as `${user_config.ENGRAM_API_KEY}`. Under the hood the plugin shells out to `npx mcp-remote` with the key passed as an env var to the bridge process.

Can I scope memory per project?

Yes. The plugin defaults to one bucket per workspace. Override the `bucket` arg on `store_memory` / `query_memory` to share memories across repos or split further.

Related integrations

Cursor Cursor desktop editor and the cursor-agent CLI share one MCP config, global or project-scoped. Read more → Codex Codex CLI plugin: vendor a plugin folder, register in marketplace.json, OAuth-on-install. Read more → Continue Continue (VS Code, JetBrains, cn CLI): YAML config, with tools that fire in Agent mode only. Read more →

Ship durable memory in Claude Code today

Free tier: 10K memories and 50K retrievals per month. No credit card. Same Engram backend powers all 41 integrations, so memories you write from one client are immediately queryable from the rest.

Start free See pricing