MCP reference for agent memory.
Connect AI agents to Dijin’s permissioned memory layer: recall approved context, verify evidence, request scopes, and propose memory without silently changing the user’s graph.
https://mcp.dijin.co/mcpThe agent memory contract
Read
Agents can recall approved summaries, entities, decisions, conflicts, and evidence.
Verify
Every grounded answer carries an evidence pack and audit trail.
Propose
Agents can propose memory through gated write scopes. Writes never go straight to the graph.
Transport & auth
Streamable HTTP
The canonical transport. One path-agnostic handler.
OAuth 2.1
PKCE + RFC 9728 discovery (mandatory) + Client ID Metadata Documents (preferred) with DCR fallback.
The 8 canonical scopes
Least privilege by default. The user grants exactly what your client needs.
memory.summaryRead high-level summaries only.
memory.decisionsRead confirmed decisions and their rationale.
memory.entitiesRead people, projects, and things in your memory graph.
memory.evidenceRead the evidence pack behind an answer.
memory.conflictsRead where claims disagree or were superseded.
memory.auditRead the tamper-evident access log.
memory.raw_source.read 🔒ProRead raw source text. Highest-trust scope. Pro-gated, device-confirmed, and never granted by default.
memory.write 🔒Promemory.write proposes memory, corrections, or links. It never silently mutates the graph; proposals pass through the worker, policy checks, and review gates.
memory.writePro-gated. Lets an agent propose memory, correction, or linkage. It never silently mutates the graph; proposals pass through the worker, policy checks, and review gates.
Verified clients
The clients we've actually seen complete a handshake, not a "works with any AI" hand-wave.
| Claude Desktop | Anthropic | Verified | MCP_SSE |
| ChatGPT (Desktop) | OpenAI | Verified | MCP_SSE |
| Cursor | Anysphere | Verified | MCP_SSE |
| Zed | Zed Industries | Verified | MCP_SSE |
| Continue | Continue.dev | Verified | MCP_SSE |
| Gemini (CLI) | Planned | MCP_SSE |
Honest caveats
What a developer needs to know before they build.
The public route is still rolling out. Self-host and local dev work today, and the hosted endpoint is being re-pointed.
A new account's graph is empty until you connect sources. Read tools return an honest empty result, not an error.
Writes never go straight to the graph. They pass through the worker, and out-of-scope requests fail closed on the server.