Glossara Get notified
Self-hosted and private

Shared memory for your agents.

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.

How it works

People and agents, working together

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.

How people and agents interact with Glossara People in a browser, agent hosts over MCP, and scripts over REST send requests through an HTTPS front door into the Glossara server. Each request passes a rate limiter, authentication and authorization before it reaches the web app, the MCP server or the REST API. Those surfaces read and write the knowledge store, which lives in your database. Background workers embed pages and type links using a model server you configure. Responses carry cited answers, tool results and the list of changes an agent asked for. A refused request bounces off authorization with its reason, and the server writes each request to the log. People Use the web app in a browser. Signed in with a session. Owner, member or viewer. Agents Claude Code, Cursor and others. Connect over MCP with a token. Limited to the spaces you choose. Scripts and services Call the REST API directly. Act for themselves or for a person. Fetch what changed since last visit. HTTPS front door · TLS Glossara server Rate limiter per address per token per write Limits enforced across all servers. Authentication who is asking? session cookie, or bearer token Access revoked when tokens expire. Authorization may they do this? role in the space token scope read or write Out of scope stays invisible. Web app edit · ask · graph MCP server /mcp · tools REST API what changed? Your knowledge Markdown pages · typed graph · search index request log · who, what, and why a request was refused · one line each session dana@… GET /spaces/…/pages 200 · 4ms token it-ops-bot POST /blocks 201 · delegated-by priya@… · 11ms token viewer-bot POST /blocks 403 · reason role-lacks:viewer:write · 2ms Database your data, your storage pages, links, log Background workers embeddings, typed links Model server any OpenAI-compatible local or hosted cited answer tool result what changed 403 role-lacks:viewer:write
People, with a session Agent hosts over MCP Scripts over REST, asking for changes Refused, with the reason logged Workers talking to your model server

Credentials stored as hashes

Glossara hashes sessions and agent tokens before storing them. It shows an agent token once, at creation, with an expiry date.

Scopes that hold

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.

Rate limits

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.

An audit trail

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.

Your model, or none

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.

Two uses, one source of truth

Shared memory for agents. Knowledge management for people.

One set of pages, one set of permissions, one log. Agents do the reading and the drafting. People decide what stands.

Shared memory for your agents

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.

Knowledge management for your team

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.

More on knowledge management