Skip to content

What is Corpus?

Corpus is a shared home for the markdown your AI agents need to do good work. Keep it in git if you like: Corpus adds a browser editor for people without repository access, agent changes that arrive as proposals a person accepts change by change, and corpus pull --all to land the approved files in your repository.

You write documents in a web editor — coding standards, architecture notes, API conventions, runbooks, product decisions — group them into a corpus, and point your agent at that corpus over MCP. Every agent on that corpus reads the same source of truth, and you update it without touching a repo.

If you use Claude Code, Cursor, or any MCP-capable agent, you already have a context problem:

  • The rules your agent should follow live in scattered markdown files, Notion pages, Slack threads, and people’s heads.
  • Each project re-pastes the same conventions into CLAUDE.md / .cursorrules, and they drift apart.
  • Non-engineers who own a lot of that knowledge can’t easily contribute to files behind a Git workflow.
  • When the canonical doc changes, nothing tells the agents.

Corpus makes one canonical copy, editable by anyone on your team in a browser, and serves it to agents on demand. No repo, no copy-paste, no drift.

Three concepts, in order:

  1. Document — one markdown file. It has a stable slug, a title, and an append-only version history. Editing it in the browser creates a new version; nothing is ever silently overwritten.
  2. Corpus — a self-contained drive: a tree of folders and markdown documents. This is the unit an agent consumes. Every document belongs to exactly one corpus. Pages that are not ready for agents sit in Drafts, the project’s built-in unpublished space.
  3. MCP endpoint — one URL per project. An agent that authenticates to it can list your corpora and read their assembled markdown (and individual documents). Agents never write canonically — the most an agent can do is file a proposal for a person to accept.

Tenancy is Organization → Project. You sign up, name your organization, and a default project is created for you. Everything — documents, corpora, team, the MCP endpoint — lives inside that project.

The same person, wearing two hats:

  • Writing it — anyone on the team, technical or not, who knows how the work should be done. No Git, no PR, just a markdown editor.
  • Consuming it — anyone running an agent who wants it to follow that knowledge. One config line and the agent has it.