Is Glen a style guide or a CMS?

No. Glen is shared memory for the AI agents you write with. It captures and applies your evolving conventions, terminology, voice, and reviewer feedback, automatically, rather than sitting in a doc you have to remember to consult.

Can my whole docs team share the same conventions memory?

Yes. Glen is org-scoped, so every writer's agent and every MCP client reads and writes one shared memory of your documentation standards.

Shared memory for technical writers

Technical writing is governed by a thousand small decisions: the house style, the term you standardized on (and the three you banned), how product names are capitalized, which audience a doc set targets, the voice the team agreed on. When you use AI agents to draft, edit, or update docs, none of that carries between sessions, so you re-paste the style guide, re-correct the same terminology, and re-explain the conventions every time. Glen, shared memory for AI agents, gives the agents writers use long-term shared memory as a single MCP tool, so your documentation conventions persist and are shared across the whole docs team.

Connect your writing tools to Glen over MCP and any agent, drafting a new page, updating a reference, or editing for consistency, can call one tool that retrieves relevant long-term context and records new facts in a single round trip. Before it writes, it pulls what the team has already decided: the approved terminology, the voice and tone rules, the structure your docs follow, the things reviewers always flag. As you correct and refine, it writes those decisions back, so the next draft, yours or a colleague's, already respects them.

The benefit is a living style memory instead of a static guide nobody rereads. Glen is org-scoped, so the conventions are shared across every writer, every agent, and every tool in your organization. A terminology call one writer's agent recorded is enforced for the whole team next time, and because Glen is a standard MCP server, the same memory is readable from Claude Code, Cursor, your docs-authoring agent, or any other MCP client. The editorial knowledge that usually lives in a wiki and your reviewers' memories becomes durable context your agents apply automatically. You connect once over OAuth or an API key and stop re-teaching your own style guide every session.

FAQ

Is Glen a style guide or a CMS?: No. Glen is shared memory for the AI agents you write with. It captures and applies your evolving conventions, terminology, voice, and reviewer feedback, automatically, rather than sitting in a doc you have to remember to consult.
Can my whole docs team share the same conventions memory?: Yes. Glen is org-scoped, so every writer's agent and every MCP client reads and writes one shared memory of your documentation standards.