
Glen
com.tryglenPublished by tryglen.comOfficial publisherv1.0.0Updated Nov 5, 2026
Search your team's shared agent memory, and use and save the org's skills and documents.
Overview
Glen gives an assistant access to your team's shared agent memory, skills and documents, so it can answer questions and save reusable knowledge.
- What you can do
- Search team memory and trace code lines back through git blame to the agent conversations that wrote them
- Find and read team skills, and look up dependencies those skills already rely on
- Search and open saved documents such as runbooks and postmortems
- Save and share skills and Markdown or HTML documents
- Import past conversations, forget or restore evidence, and set recording mode and skill suggestions
- Invite teammates, delete your own skills and documents, and send feedback
- When to use it
- Useful when a team already keeps its coding-agent history in Glen and wants assistants to answer questions like why a decision was made or what broke last time, and to reuse shared skills and runbooks. Not needed for solo work without a Glen team.
- Requirements
- A hosted remote endpoint; nothing to install. Sign-in uses OAuth on first connect, where you log in and pick a team. Scripts can instead use an API key created in the Glen dashboard, sent in the x-api-key header with the organization id in x-glen-org-id. Works on the free plan.
Installation
In SourceWeft
- Open Glen in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.tryglen%2Fglen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"glen": {
"type": "http",
"url": "https://mcp.tryglen.com/mcp"
}
}
}README
Glen MCP server
Your team's coding agents figure things out all day: why a bug happened, which approach got thrown out, who decided what. Glen keeps all of that in one shared memory for your whole team. This MCP server lets any MCP client tap into it. You can ask it questions, use your team's saved skills and documents, and save new ones.
There's nothing to install or run. Glen hosts the server, so you just point your client at this URL and sign in:
The first time you connect, your client opens Glen's sign-in page. You log in, pick which team's memory to use, and you're done. It works on the free plan.
If you'd rather use an API key (for scripts, say), make one under Settings → API keys in the Glen dashboard and send it in the x-api-key header, along with your organization's id in x-glen-org-id.
Connect your client
Claude (web, desktop or mobile): go to Customize → Connectors, add a custom connector, and paste the URL above. Step-by-step guide
ChatGPT: go to chatgpt.com/plugins, hit +, choose Add custom MCP server, paste the URL and pick OAuth. Step-by-step guide
Claude Code:
Cursor, or anything else that reads an mcp.json:
Using a coding agent like Cursor or pi day to day? The glen plugin is probably a better fit than this server on its own. It also records your sessions into team memory, so your work helps the next person. See the Cursor and pi guides.
What you can do
Ask things like "why did we move search off Elasticsearch?" or "what broke last time someone touched the payments webhook?" and Glen answers from your team's history, with sources you can click through to.
You can also find and run your team's skills (reusable instructions an agent can follow), save new ones, and keep documents like runbooks and postmortems in a shared library.
Here's every tool. Each one tells your client whether it only reads or also changes something, so your client can ask you before anything gets written.
Want the details, like inputs, outputs, rate limits and error messages? It's all in the MCP server reference.
A couple of things to know
Glen only ever shows you things you could already see in the Glen dashboard, and only from the team you connected to. Tools that write act as you, on your own stuff.
Glen's answers are written by an AI model, so they can be wrong or out of date. Each one links to its sources, so check anything important before you act on it.
Privacy and help
- Privacy policy and sub-processors
- Questions or problems: [email protected]
- Security issues: [email protected]
This repo only describes the hosted server. Glen's code isn't open source, so there's no code here to run.
Source: README.md at commit 93a661f
Tools
0Version history
1- v1.0.0LatestNov 4, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
