Shared memory for VS Code

VS Code's agent mode is an MCP client: it registers servers under a servers key and can connect to both local and remote MCP servers, including ones that authenticate over OAuth. That makes it a natural fit for Glen, shared memory for AI agents. Without it, every Copilot or agent session in VS Code starts from a blank slate, unaware of the conventions, decisions, and pitfalls that you or your teammates already worked through. Glen gives your team's VS Code instances a single, organization-wide memory they all share.

Add Glen as an MCP server in VS Code and the agent gets one memory tool that reads relevant context and writes new observations in the same call. As you code, the things worth remembering, why a module is structured the way it is, which APIs are off-limits, what broke last time, get captured into the org's shared store. The next time anyone on the team works in a related area, VS Code's agent surfaces that knowledge automatically instead of making the same discovery again.

Because Glen memory is scoped to the organization rather than to a single developer, it turns individual learnings into team assets. A teammate who has never opened a particular service still benefits from everything other people's agents have recorded about it, and a new hire's VS Code inherits the full memory on day one. VS Code's native support for remote MCP servers means setup is just adding the server and completing the OAuth flow once; from there, the memory grows quietly as the team works, and there is no per-user store to provision or maintain. The result is a coding assistant that gets smarter about your codebase the more your whole team uses it.

Add Glen to VS Code

Add to .vscode/mcp.json

.vscode/mcp.json
json
{
  "servers": {
    "glen": {
      "type": "http",
      "url": "https://tryglen.com/api/mcp"
    }
  }
}

FAQ

Does VS Code support remote MCP servers like Glen?
Yes. VS Code's agent mode connects to remote MCP servers natively and supports OAuth, so you add Glen under the servers key and authorize it once.
Is the memory per-developer or shared?
It is shared. Glen is org-scoped, so every teammate's VS Code reads and writes the same memory and inherits what others have learned.