Zed Integration Guide

Give Zed’s agent persistent memory across sessions using Engram. Recent Zed versions support remote MCP servers natively — setup is one config block.

Setup

1. Add the context server

Open your Zed settings.json (Cmd+, → “Open Settings”) and add:

{
  "context_servers": {
    "engram": {
      "url": "https://mcp.getengram.app/mcp"
    }
  }
}

With no Authorization header configured, Zed prompts you through Engram’s OAuth sign-in on first use — no API key needed.

Prefer an API key? Sign up at getengram.app , create a key, and add:

{
  "context_servers": {
    "engram": {
      "url": "https://mcp.getengram.app/mcp",
      "headers": {
        "Authorization": "Bearer engram_sk_live_your_key_here"
      }
    }
  }
}

2. Verify

Open the Agent Panel and ask Zed to search Engram. If it can call the search tool, you’re connected.

Older Zed versions

If your Zed build predates native remote-MCP support, bridge with mcp-remote:

{
  "context_servers": {
    "engram": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.getengram.app/mcp"]
    }
  }
}

Using memory in Zed

Ask the agent naturally:

• “Remember this” — stores the current exchange verbatim via append_messages
• “What do you remember about the auth refactor?” — searches your memory with search
• Context saved from ChatGPT, Claude Code, or Cursor is available here too — it’s one memory across every tool you connect.