Where does Glen go in Zed's config?

Register it under the context_servers block in Zed's settings, authenticating over OAuth or an API key. Zed's agent then has one tool to read and write shared memory.

Does Glen fit Zed's collaborative model?

Yes. Glen memory is org-scoped, so what one collaborator's Zed learns is shared with everyone in the organization, mirroring how Zed handles real-time collaboration.

Shared memory for Zed

Zed is the high-performance, collaborative code editor built for speed, with an agent panel and native MCP support that registers servers under context_servers in its settings. Its whole pitch is low friction, so it is jarring when the AI assistant inside it has no continuity: every Zed session forgets the project conventions, the architectural reasoning, and the gotchas it, or a teammate's Zed, worked out before. Glen, shared memory for AI agents, restores that continuity by giving every Zed in your organization one shared memory they all read from and write to.

Add Glen to Zed's context_servers and the agent gains a single tool that retrieves and records in one round trip. When you ask Zed's assistant to make a change, it first pulls the context relevant to the code in front of you, the patterns, the constraints, the prior decisions, so its suggestions match how your team builds rather than starting from a blank slate. Anything new it learns during the session is written straight back to the organization's shared store.

Zed leans hard into real-time collaboration, multiple people in the same project, so memory that lives on one machine misses the point. Glen is org-scoped: the facts one developer's Zed records are immediately available to every teammate's Zed, matching the collaborative model Zed is designed around. And because Glen speaks standard MCP, the same memory is readable by your Cursor, VS Code, or Claude Code agents too, so knowledge follows the work across editors. Setup is a single context_servers entry authenticated over OAuth or an API key, and from there the memory compounds as a byproduct of normal editing.

Add Glen to Zed

Add to ~/.config/zed/settings.json

~/.config/zed/settings.json

json

{
  "context_servers": {
    "glen": {
      "source": "custom",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://tryglen.com/api/mcp"
      ]
    }
  }
}

Heads up

Zed is stdio-only; this bridges the remote server with `mcp-remote`.

FAQ

Where does Glen go in Zed's config?: Register it under the context_servers block in Zed's settings, authenticating over OAuth or an API key. Zed's agent then has one tool to read and write shared memory.
Does Glen fit Zed's collaborative model?: Yes. Glen memory is org-scoped, so what one collaborator's Zed learns is shared with everyone in the organization, mirroring how Zed handles real-time collaboration.