Integration

Long-term memory for Windsurf

Cascade, Windsurf's editor agent, is great at multi-file refactors but starts every conversation amnesiac. Architecture decisions, the rejected approaches, the things you taught it last week: all of it evaporates the moment you close the tab. Add Engram to `mcp_config.json` once and Cascade picks up where it left off.

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 Windsurf.

Three steps to memory in your agent

Sign up. Free, no card. You'll land on a Getting Started page that walks the next two steps.
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.
Paste the snippet below into your agent and restart it. Use Authorization: Bearer <api-key>with the API key from your portal.

engram-windsurf: Cascade agent

Wires six Engram MCP tools into Cascade, Windsurf's AI editor agent. Source: github.com/lumetra-io/engram-windsurf.

Edit ~/.codeium/windsurf/mcp_config.json (same path on macOS, Linux, and Windows) and merge in the engram block:

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "engram": {
      "serverUrl": "https://mcp.lumetra.io/mcp/sse",
      "headers": {
        "Authorization": "Bearer <api-key>"
      }
    }
  }
}

Restart Windsurf or click Refresh in the Cascade MCP panel.
Verify: Cascade panel → top-right MCPs icon. engram should appear with a green status dot and six available tools on hover. Cascade asks once to approve the server on first tool use.

What you can do once memory's wired in

Recall the design choices from our last refactoring conversation
Remember the codebase conventions you've taught Cascade (file structure, naming, error handling style)
Pull up the API surface we agreed on for the new microservice last Thursday
Avoid re-explaining why we chose Postgres over MongoDB for this project

FAQ

Where does Windsurf look for the MCP config?

`~/.codeium/windsurf/mcp_config.json`, same path on macOS, Linux, and Windows.

How do I verify it's connected?

Open the Cascade panel and click the MCPs icon in the top right. `engram` should appear with a green status dot and six tools listed on hover. On first tool use Cascade asks once to approve the server.

Does the `mcpServers.engram` field need to be `url` or `serverUrl`?

Either works. Windsurf accepts both `serverUrl` and `url` as aliases for remote HTTP MCPs. Our snippet uses `serverUrl` to match Windsurf's docs; a Cursor-style `url` snippet will also work. The rest of the block (`headers`, etc.) still has to be Windsurf-shaped, so don't blindly copy a full Cursor config.

Related integrations

Ship durable memory in Windsurf 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