Four copies of the truth
A rules file here, a config there, a third on the other laptop. All drifting.
Organizational memory · live now
One memory. Every tool.
Claude Code, Cursor, Codex and every MCP client read and write the same cloud memory. Connect once — every tool and every agent inherits it.
Stop re-explaining your codebase.
No credit card · connects in about a minute.
0.94
payments-api depends on ledger-service PR #812
0.88
ADR-0014 supersedes ADR-0009 Decision
0.91
Retry storm caused INC-231 Incident
0.86
Priya owns billing/reconcile.go 31 commits
0.79
The pgbouncer pin blocks Postgres 16 Open
One memory, shared by
- Claude Code
- Cursor
- Codex
- Windsurf
- Cline
- Zed
- Any MCP client
The problem
Every tool remembers a little. Nothing remembers the whole thing.
So every session starts cold, and the only complete copy of your system is in someone's head.
Nothing sees what shipped
The answers live in your PRs, incidents and decisions. No assistant reads them.
You are the index
Interrupted all day, because you're the only one who remembers why.
Setup
One endpoint. Nothing to migrate.
Add the endpoint
One command. Your client detects OAuth and opens the browser to approve. No key to copy.
Connect a repo
Corpus reads the history and builds the memory. Once.
Every tool inherits it
Ask in one, continue in another. Nothing gets re-explained.
codex mcp add edgex-memory --url https://console.edgex11.com/api/v1/runtime/mcpclaude mcp add --transport http edgex-memory https://console.edgex11.com/api/v1/runtime/mcp
claude mcp login edgex-memoryYour client detects OAuth, registers itself and opens the browser to approve. Clients without OAuth support, such as Cursor, use a key from the console instead. Full MCP documentation ›
Engineering workflows
The questions that cost you hours.
Answered from your own history — with the PR or decision it came from.
“What do I need to know before touching billing?”
Onboarding, without the six-week ramp.
“Why is it built like this?”
Decisions keep their reasons — and what replaced them.
“Have we seen this outage before?”
Every incident keeps its root cause and its fix.
“What's risky about this diff?”
Review with the defect history the diff doesn't show.
“What still calls v1 auth?”
Blast radius across every repo, in one question.
“Where did we get to yesterday?”
Switch tools mid-task without re-explaining.
Proof
We run our own engineering org on it.
Corpus holds EdgeX11's own decisions, incidents, defects and ownership. Live numbers from that workspace, today.
2,800entities
2,118facts
215conventions captured
266facts learned this week
Every answer cites its sourceNewer facts supersede older onesMemory never leaves your workspaceDelete a source, everything derived goes
Questions
Before you start.
Which tools work with it?
Any client that speaks MCP — Claude Code, Cursor, Codex and the rest. They all point at one endpoint and share the same memory.
How long does setup take?
About a minute, and there is no API key to copy. One command, then your client opens the browser for you to approve. Nothing to migrate.
Why not just use a CLAUDE.md?
A rules file is a copy per tool that goes stale, and it only holds conventions. Corpus is one memory every tool reads and writes, and it also holds decisions, incidents and ownership. With one repo, one tool and one person, a rules file is genuinely enough — we'd rather say so.
How is this different from Mem0 or Zep?
Those are memory infrastructure for an agent product you are building — you integrate them into your own app. Corpus is memory for the tools your team already works in: connect it once and Claude Code, Cursor and Codex share it. Different job, and plenty of teams will want both.
How do I know an answer is right?
Every fact cites its source and carries a confidence score, and newer facts supersede older ones rather than overwriting them.
Can I keep client work separate?
Yes. A workspace is a team plus its repositories, and memory never crosses that boundary.
What does it cost?
Free to start: one repository, every tool, no credit card. See pricing.