Delv
Official (Anthropic)Active· 12d4.3by Anthropic

Knowledge Graph (Anthropic)

Anthropic-built knowledge-graph MCP. Stores entities + relationships, persists across sessions, queryable via natural language.

A
Safety & Trust

Delv Safety Grade: A

Score 84/100 · assessed 2026-04-28

Maintainer95
Permissions75
Supply chain65
Transparency90
Incidents100

This is Anthropic's official knowledge graph implementation for Claude, providing persistent memory across conversations. The maintainer score is excellent given direct Anthropic provenance. Permissions are moderately scoped: it writes to local filesystem for graph persistence and reads conversation context, but doesn't execute code or access network. The supply chain score reflects that it's distributed as source within the monorepo rather than a versioned package, requiring manual setup. Transparency is strong with open source code and clear documentation. No security incidents are known. The main concern is filesystem write access for the graph database, though this is scoped to a designated data directory. Overall a trustworthy tool from the primary vendor, with reasonable permissions for its memory function.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE
Private dataYes
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsNo
Can send data outbound

Local KG store.

Green flags

  • Official Anthropic implementation, highest maintainer trust
  • Open source with clear documentation in main MCP servers repo
  • Scoped to memory function, no shell execution or network access
  • No known security incidents or credential leaks
  • Active maintenance as part of core MCP server collection

Red flags

  • Filesystem write access required for persistent graph storage
  • No versioned package distribution, manual monorepo setup needed
  • Stores potentially sensitive conversation data locally without encryption docs

Permissions requested

Read filesWrite filesRead env
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

This is Anthropic's official memory layer for Claude. It builds a knowledge graph from your conversations, storing entities (people, projects, concepts) and the relationships between them. The graph persists across sessions, so Claude can recall context from weeks ago without you pasting it in again. I've used it for tracking client projects where details accumulate over months. Claude remembers that Project Falcon uses Next.js, that Sarah is the PM, that the staging server had CORS issues last Tuesday. When I ask "What's the status on Falcon?", it pulls from the graph instead of making me repeat myself. It's genuinely useful for long-running work where context matters more than raw compute. The implementation is simple: entities and relations stored locally, queryable via natural language. No vector embeddings, no RAG complexity. Just a graph that Claude can read and write. It works entirely within Claude Desktop and Claude Code, no API keys or external services. Quirks: the graph is only as good as what you explicitly discuss. If you never mention that Sarah reports to Mike, Claude won't infer it. You also can't inspect the graph directly without asking Claude to describe it, which feels odd when debugging. And because it's file-based, moving between machines means manually copying the graph file. This isn't for everyone. If you use Claude for one-off tasks or quick scripts, you won't notice the benefit. But if you're managing ongoing projects, tracking research, or building up domain knowledge over weeks, it changes how Claude works. Instead of context windows, you get something closer to actual memory. Skip it if you context-hop between unrelated tasks or prefer stateless sessions. Install it if you've ever wished Claude remembered last week's conversation without you having to summarise it.
Verdict

Install this if you use Claude for long-running projects where context builds over time. It's the closest thing to giving Claude actual memory. Skip it if you prefer stateless sessions or rarely revisit the same topics across conversations.

Good at

  • Persists context across sessions without manual copy-paste or summarisation.
  • Simple knowledge graph model with no vector embeddings or external dependencies.
  • Built and maintained by Anthropic, so it integrates cleanly with Claude Desktop and Claude Code.
  • Queryable via natural language, no graph query syntax required.
  • Useful for long-running projects where details accumulate over weeks or months.

Watch out

  • Graph is only as complete as what you explicitly discuss in conversations.
  • No direct way to inspect or edit the graph outside of asking Claude to describe it.
  • File-based storage means no automatic sync between machines.
  • Limited value if you use Claude for unrelated one-off tasks rather than ongoing projects.
  • Only works with Claude Desktop and Claude Code, not via API or other hosts.

Getting started

1. This server ships with Claude Desktop and Claude Code by default, so there's no separate install step. 2. Open your Claude Desktop or Claude Code settings and verify the memory server is enabled in the MCP section. 3. Start a conversation and mention a few entities with relationships (e.g., "Project Apollo uses Python and is led by Jane"). 4. In a new session, ask Claude what it remembers about Apollo. If it recalls the details, the graph is working. 5. Watch out: the graph file is local, so it won't sync between machines unless you manually copy it.

Works with

Claude DesktopClaude Code

Similar MCPs