Does Glen index my code like Sourcegraph does?

No. Sourcegraph indexes and searches code; Glen stores durable human knowledge about it, decisions, ownership, gotchas, as org-shared memory over MCP. They are complementary.

How does my team reach Glen alongside Sourcegraph?

Glen is a standard MCP server. Connect it as an MCP tool in your agents and editors, authenticate over OAuth or an API key, and the same memory is shared across everyone.

Shared memory for Sourcegraph

Sourcegraph and its assistant give engineers code search and AI help across huge, multi-repository codebases, the right context about where code lives and how it fits together. What the assistant does not retain is the durable, human knowledge that surrounds the code: why a module is structured the way it is, which service owns a flaky endpoint, the decision a team made that the code itself does not explain. That knowledge gets re-derived every session and rarely shared between engineers or tools. Glen, shared memory for AI agents, adds an org-scoped long-term memory layer over MCP, so the context an engineer or agent builds while working in Sourcegraph persists and is shared.

Sourcegraph is unmatched at telling you what the code is. Glen captures what the team knows about it. Used alongside Sourcegraph, Glen gives your agents and engineers one MCP tool that both retrieves accumulated knowledge, the ownership, the gotcha, the past decision, and records new facts as they are discovered during code search and review. The next investigation starts with that institutional memory instead of rebuilding it from the diff.

Because Glen is org-scoped, that knowledge is shared across every engineer and every agent in the organization, not trapped in one person's session. One engineer's agent learns why a subsystem behaves a certain way; a teammate's agent, or a human in Claude Code or Cursor, reads it the next time they touch that code. That is the layer code intelligence does not provide: durable human context that outlives a session and is shared across people and tools. And because Glen is a standard MCP server, the memory written while working with Sourcegraph is readable from any other MCP client, so code search, AI review, and editor work all draw on the same growing understanding of your codebase. Wire it in once over OAuth or an API key and let the team's knowledge compound alongside the code graph.

FAQ

Does Glen index my code like Sourcegraph does?: No. Sourcegraph indexes and searches code; Glen stores durable human knowledge about it, decisions, ownership, gotchas, as org-shared memory over MCP. They are complementary.
How does my team reach Glen alongside Sourcegraph?: Glen is a standard MCP server. Connect it as an MCP tool in your agents and editors, authenticate over OAuth or an API key, and the same memory is shared across everyone.