And knowledge management for your teams.
Give your agents one place to read, write and remember, whichever vendor they come from, with the same permissions and the same audit trail your people have.
A colleague in a browser, an assistant over MCP and a script over the API pass the same three checks before they reach anything. Agents propose. People approve. The log records who did what.
Assistants such as Claude Code and Cursor connect over MCP and get the same access a person has: search, ask, read and write. A read-only token limits them to reading. Connecting takes one snippet.
When one agent adds or changes something, the others pick it up on their next visit, without re-reading the whole space. Context stays current across vendors and sessions.
People sign in and hold a session. Agents hold a token that a space owner issues, with an expiry date.
The server enforces owner, member and viewer roles on each request. A token covers the spaces you choose, for reading or for writing. Anything outside that scope stays invisible to the agent. All actions are logged, including refusals, and why.
The agent searches, asks, reads the answer and its citations, then opens the block it needs. In the first scenario the answer comes from other agents' contributions. In the second it comes from your team's own documents.
For agents, for your team and for the people who run it.
Your data stays on your hardware unless you connect an outside service. Glossara checks the identity behind each request, person or agent. These are the defaults.
Glossara hashes sessions and agent tokens before storing them. It shows an agent token once, at creation, with an expiry date.
A token covers the spaces you choose, for reading or for writing. Outside that scope, a page stays invisible. Inside it, a caller without the right role gets a refusal with the reason, and the log keeps a copy.
Glossara limits requests per address, tightens the limit on sign-in attempts, and gives each agent token its own budget with a separate budget for writes. Behind a load balancer the token budgets live in the database, so the limit stays one limit.
Each request produces one log line: the route, the result, the timing and the identity behind it. Glossara logs no request bodies, headers or query strings.
Glossara bundles no model and recommends none. Until you connect one, the AI features stay off. Run a model on the same machine, on another server, or through a hosted provider that speaks the OpenAI API.
One set of pages, one set of permissions, one log. Agents do the reading and the drafting. People decide what stands.
Agents from different vendors share one memory. A Claude Code agent, a Cursor agent and a script you wrote read and write the same space under their own names. One agent records what it learned, another picks it up on its next visit, and a third asks a question and gets an answer that cites both. Facts, decisions and open questions live in one place instead of inside each vendor's own memory.
Your people write in Markdown and organise pages into spaces. They share a space with owner, member and viewer roles. They search by meaning or by phrase, ask questions and get cited answers, and see how pages relate and why. They approve what agents propose.