Do my SEs each need their own memory setup?

No. Glen is org-shared, so every solutions engineer's agents read and write the same store. Account context one SE captures is immediately available to the rest of the team.

Which tools can use Glen?

Any MCP client. Whatever your SEs use to draft POC plans, answer technical questions, or summarize calls, if it speaks MCP it can call Glen to retrieve account context and record new facts in one round trip.

Shared memory for solutions engineers

Solutions engineers carry the technical context of every active deal: the prospect's stack, the integration they tried in the POC, the objection their security team raised, the workaround that finally unblocked the demo. That knowledge lives in your head, in scattered call notes, and in Slack threads no one can find later, so when a teammate inherits the account or the deal comes back six months on, everything has to be rediscovered. When you bring AI agents into the workflow, to draft POC plans, answer technical questions, or summarize discovery calls, they start blank every time too. Glen, shared memory for AI agents, gives your agents a durable, team-shared memory as a single MCP tool, so the technical context of every account is captured once and reused by every agent and every SE on the team.

Connect Glen to the agents your solutions engineering team already uses, in Claude Code, Cursor, a custom assistant, or anything that speaks MCP, and each agent gets one tool that retrieves the relevant account context and records new facts in one round trip. Before an agent drafts a follow-up or a POC plan, it pulls what the team already knows about that prospect: the architecture they run, the constraints procurement imposed, the feature that won the technical evaluation. After a discovery call, it writes back the new requirements and blockers it surfaced. The next agent, run by you or by the SE covering for you, starts with that context instead of from zero.

The payoff is that account knowledge stops evaporating between calls and between people. Glen is org-scoped, so the memory is shared across every solutions engineer and every agent on the team rather than locked to one person's notes. One SE's agent learns that a prospect requires SSO before they will sign; every other agent knows it next time the account comes up. Because Glen is a standard MCP server, the same memory is readable from any MCP client, so whether the work happens in a coding agent, a sales assistant, or a notes summarizer, it all draws on one shared record of the deal. You wire it in once over OAuth or an API key and let the technical context of every account compound instead of resetting with each handoff.

FAQ

Do my SEs each need their own memory setup?: No. Glen is org-shared, so every solutions engineer's agents read and write the same store. Account context one SE captures is immediately available to the rest of the team.
Which tools can use Glen?: Any MCP client. Whatever your SEs use to draft POC plans, answer technical questions, or summarize calls, if it speaks MCP it can call Glen to retrieve account context and record new facts in one round trip.