How do I add Glen to Claude Desktop?

Register Glen as an MCP server in Claude Desktop's configuration, authenticating over OAuth or an API key. The assistant then has one tool that reads and writes shared memory.

Does memory carry over between Claude Desktop chats?

Yes. Glen persists facts in your organization's shared store, so a new conversation, on the same desktop or a teammate's, can pull what earlier ones established.

Shared memory for Claude Desktop

Claude Desktop is where a lot of people do their thinking out loud, drafting, planning, analyzing, asking the same model the same kinds of questions day after day. It was one of the first apps to support MCP, registering servers in its config so the assistant can reach external tools. But each new conversation in Claude Desktop is a blank slate: it does not remember the decisions you reached last week, the preferences you established, or what a colleague's Claude Desktop worked out on the same project. Glen, shared memory for AI agents, closes that gap by giving every Claude Desktop in your organization one memory they all read from and write to.

Connect Glen as an MCP server in Claude Desktop and the assistant gets one tool that, in a single round trip, both surfaces what is already known and records what it just learned. Start a fresh chat about a project and Claude Desktop can pull the relevant history, the conclusions, the constraints, the context, instead of asking you to re-explain it. When the conversation produces a new decision or fact worth keeping, it writes that back to the shared store automatically.

The org-scoped design is what makes this more than per-app history. Because the memory belongs to your organization rather than to one desktop install, a teammate who opens Claude Desktop and asks about the same initiative inherits everything you and others have already established. That turns Claude Desktop from an isolated thinking tool into a shared one: research, planning, and analysis compound across people instead of restarting with every window. And because Glen works with any MCP client, the memory your Claude Desktop builds is the same memory your Claude Code, Cursor, or VS Code agent reads, so the knowledge follows the work across tools. Setup is one MCP server entry connected over OAuth or an API key.

Add Glen to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

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

Heads up

Claude Desktop's config is stdio-only; this bridges the remote server with `mcp-remote`. (Pro/Team plans can use native Connectors instead.)

FAQ

How do I add Glen to Claude Desktop?: Register Glen as an MCP server in Claude Desktop's configuration, authenticating over OAuth or an API key. The assistant then has one tool that reads and writes shared memory.
Does memory carry over between Claude Desktop chats?: Yes. Glen persists facts in your organization's shared store, so a new conversation, on the same desktop or a teammate's, can pull what earlier ones established.