One context, cut into a slice per agent.

Many tools set access per user or per document. Substrate sets it per fact, per agent.

Summary by kind of tool

Assistant memoryChatGPT memory, Claude memoryMemory APIsMem0, Zep, LettaWikis and docsNotion, ConfluenceEnterprise searchGleanNotes filesCLAUDE.md, AGENTS.mdSubstrate
A slice per agent, cut by factnononopartialnoyes
One change reaches every connected agentnopartialnopartialnoyes
People can edit itpartialnoyesnoyesyes
You own itnopartialyespartialyesyes
Works with any MCP agentnoyespartialpartialpartialyes

Partial: access is set per user or per document, not per fact. Based on public documentation, November 2026.

A named product can do more than its category. Where its documentation shows that, it gets the higher mark below.

Where Substrate’s “yes” comes from.

A slice per agent, cut by fact

A rule per agent, in plain English. The bank is cut by fact, not by document. Permissions

One change reaches every connected agent

Connected agents have the change on their next read. How it works

People can edit it

Every page is a document you can read and edit. How it works

You own it

Export everything whenever you like. FAQ: export

Works with any MCP agent

MCP clients connect by link. Claude Code, Cowork, Codex and Hermes use plugins. Connect

Assistant memory

Sources read .

ChatGPT memory

Remembers across your chats without setup.

Slice per agentno

One general memory setting, separate from per-app permissions.

Connected apps in ChatGPT; Memory in ChatGPT

One changepartial

Apps inside ChatGPT may use memories. Outside agents are not described.

Connected apps in ChatGPT

People editpartial

You can edit saved memories where the controls are available.

Memory in ChatGPT

You own itnot verified

The export page does not say whether memories are included. The category mark, “no”, is not a statement about this product.

Exporting your ChatGPT history and data

MCPno

No way is described for an outside MCP client to read it.

Memory in ChatGPT; Connected apps in ChatGPT

Claude memory

Memory you can open and edit by topic, kept per project.

Slice per agentpartial

Split per project, not per agent or per fact.

Chat search and memory

One changepartial

Shared between Chat and cloud Cowork. Other vendors' agents are not covered.

Chat search and memory

People edityes

Chat search and memory

You own itpartial

Included in data exports. Import is marked experimental.

Chat search and memory; Importing and exporting your memory

MCPno

No way is described for an outside MCP client to read it.

Chat search and memory

Memory APIs

Sources read .

Mem0

An open-source core you can run yourself, and a hosted MCP server.

Slice per agentpartial

Memories are tagged by user, agent, app and run. The caller chooses the filters.

Entity-scoped memory

One changepartial

Agents read updates through an API a developer integrates.

Update memory

People editpartial

The changelog lists memory editing in the dashboard (June 2025).

Platform changelog

You own itpartial

The open-source version is self-hosted. Hosted export runs as filtered jobs.

Open source overview; Memory export

MCPyes

Mem0 MCP

Zep

Enforced access control: default-deny policies per API key, roles and audit logs.

Slice per agentpartial

On Enterprise, policies per API key can hide single facts, by attributes set at ingestion.

Attribute-based access control

One changepartial

A fact is updated through the SDK. MCP clients read the signed-in member's graph.

Update edge; Use Zep in Claude and ChatGPT

People editnot verified

Docs show editing through the SDK and command line. We found no page showing a person editing in the web app. The category mark, “no”, is not a statement about this product.

Role-based access control

You own itpartial

The Graphiti engine is open source. No full export command is documented.

getzep/graphiti; FAQ

MCPyes

Context MCP server

Letta

Memory as plain Markdown in git. Agents can run on your own infrastructure.

Slice per agentpartial

Whole memory repositories are attached to an agent. No rule per fact.

Repositories

One changepartial

An agent commits and pushes changes; other agents pull them.

Shared memory

People editpartial

Git-backed files you edit through developer tools.

Memory

You own itpartial

Self-hostable; memory is Markdown in git.

Self-hosting

MCPpartial

The hosted MCP server messages agents. It has no tools that read memory directly.

Hosted MCP

Wikis and docs

Sources read .

Notes files

Sources read .

CLAUDE.md

Plain Markdown versioned with your code, with rules scoped by path.

Slice per agentpartial

Files apply by scope and path, not per agent or per fact.

Memory

One changepartial

A project file reaches teammates through source control.

Memory

People edityes

Memory

You own ityes

Memory

MCPpartial

Read by Claude Code. Shared with other tools through AGENTS.md, not over MCP.

Memory

AGENTS.md

An open, vendor-neutral convention many coding agents read. No infrastructure.

Slice per agentpartial

Nested files apply by directory. Every agent reads the same file.

agents.md

One changepartial

One file works across many coding agents within a repository.

agents.md; AGENTS.md

People edityes

agents.md

You own ityes

agents.md

MCPpartial

Read as a file by many coding agents. Not served over MCP.

agents.md

How this was checked.

Each answer comes from the product’s own public documentation, read on . Out of date? Tell us and we will correct it.

Start free

7 days free, no card. Then $20 a month.