Does Glen work with Windsurf's Cascade agent?

Yes. Glen is a standard MCP server, so Cascade calls it like any other MCP tool, retrieving relevant context before it plans and writing new facts back as it works.

Is the memory specific to my Windsurf install?

No. Glen memory is scoped to your organization, so what one teammate's Windsurf learns is available to everyone else's Windsurf, and to any other MCP client they use.

Shared memory for Windsurf

Windsurf's Cascade agent is built to take the wheel: it reads across your repo, plans multi-file edits, and runs flows that can span dozens of steps. But every Cascade session starts from zero on the things that are not in the code itself, the reasons behind a pattern, the deploy quirk that bit you last sprint, the convention a teammate's Windsurf settled on yesterday. Windsurf speaks MCP natively, registering servers in its config, which makes it a natural home for Glen, shared memory for AI agents. Glen turns those hard-won, undocumented facts into memory every Windsurf instance on your team can draw on.

Add Glen as an MCP server in Windsurf and Cascade gains a single tool that both retrieves and records in one round trip. When Cascade is planning a refactor, it first pulls the context relevant to the files it is about to touch, the architectural decisions, the do-not-do warnings, the naming rules, so its plan reflects what your team already knows rather than guessing from scratch. As it works and learns something new, that observation is written straight back into the organization's shared memory.

Because Glen is org-scoped, not tied to one machine or one developer, the payoff grows with the team. The agentic depth that makes Windsurf powerful also means it makes more consequential decisions per session, so feeding it accurate, accumulated context matters more, not less. One teammate's Cascade learns why a service must never run on the edge, and every other teammate's Windsurf inherits that the next time it plans work near that code. Wiring it up is a single MCP server entry, connected over OAuth or an API key; from there the memory compounds as a byproduct of normal Cascade flows, with nothing to maintain.

Add Glen to Windsurf

Add to ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "glen": {
      "serverUrl": "https://tryglen.com/api/mcp"
    }
  }
}

Heads up

Windsurf uses `serverUrl` for remote servers.

FAQ

Does Glen work with Windsurf's Cascade agent?: Yes. Glen is a standard MCP server, so Cascade calls it like any other MCP tool, retrieving relevant context before it plans and writing new facts back as it works.
Is the memory specific to my Windsurf install?: No. Glen memory is scoped to your organization, so what one teammate's Windsurf learns is available to everyone else's Windsurf, and to any other MCP client they use.