Start here
What Memrio is
Memrio is a human-governed knowledge base that AI agents read over MCP. Learn the model: workspaces, pages, page sets, agents, keys, and review.
Memrio is the approved source of truth your AI agents read from. People write and approve pages. Agents connect over the Model Context Protocol (MCP) with a scoped API key and see only the pages a human published into their page set.
It replaces the pattern of pasting policies into system prompts, or pointing a retrieval pipeline at a wiki nobody trusts. Pages are small, curated, and carry explicit instructions about when an agent should use them.
The model#
| Concept | What it is |
|---|---|
| Organization | Your company. Members have a role: owner, admin, editor, or viewer. |
| Workspace | A knowledge base inside the organization with its own slug, pages, agents, and review settings. The MCP URL is per workspace. |
| Page | A unit of knowledge with a title, tags, structured content, an owner, and a status: draft, in review, published, or archived. Pages nest in a tree. |
| Instruction | A block on a page telling agents how and when to apply it (critical, high, or normal priority). Instructions ride along with the page when an agent fetches it. |
| Document | An uploaded file (PDF, spreadsheet, image) attached to a page. Extracted text is packed into the page for agents. |
| Agent | A named consumer — “Support bot”, “Cursor (Platform team)” — with a page set, permissions, and API keys. |
| Page set | The pages an agent may read. Pick pages or whole subtrees. Everything else is invisible to that agent. |
| API key | A Bearer token bound to one agent in one workspace. The key alone tells the server what may be read. |
| Version | Every publish creates a numbered version with a change summary. Agent edits become versions waiting for review. |
Page lifecycle#
- Draft — someone (or an agent with write access) creates or edits a page. Agents cannot see drafts unless a test agent has “Read drafts” on.
- In review — a version is submitted. Reviewers approve or reject with a note.
- Published — the approved version is what every agent in the page set reads. A review frequency keeps it fresh.
- Archived — hidden from agents and browse, kept for history.
What an agent actually receives#
Agents do not receive embeddings or ranked chunks. They receive a catalog — every page title plus its “use when” instructions — and then whole pages on request. A packed page looks like this:
# Refund policy
## Instructions
[CRITICAL] Never promise a refund before checking the order date.
[HIGH] Annual plans: pro-rate to the day; monthly plans: no partial refunds.
## Content
Customers may request a refund within 30 days of purchase…
## Attached files
[FILE] refund-exceptions-2026.pdf
…extracted text…