1. Home
  2. MCP Knowledge Graph
  3. MCP Knowledge Graph for Claude Desktop: Setup & Config

Data as of

MCP Knowledge Graph for Claude Desktop: Setup & Config

Claude Desktop: Keep assistant memories as local entities, relationships, and facts across conversations.

What you can do with MCP Knowledge Graph in Claude Desktop

Choose it for local relational memory with separate project, global, and topic-specific stores.

  • Remember project facts and relationships between assistant sessions.
  • Separate work and personal memories using named databases.

Before you start: MCP Knowledge Graph in Claude Desktop

  • Node.js 22 or newer
  • An MCP-compatible AI platform

Replace the sample global memory path with your chosen directory. A project-root directory named exactly .aim takes priority when detected. Named contexts create additional JSONL databases automatically.

MCP Knowledge Graph Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For MCP Knowledge Graph, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add MCP Knowledge Graph to Claude Desktop

    Use the mcp-knowledge-graph entry below in mcpServers. Keep MCP Knowledge Graph's documented stdio connection fields and your other Claude Desktop entries.

  3. Check MCP Knowledge Graph in Claude Desktop

    MCP Knowledge Graph: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "mcp-knowledge-graph": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-knowledge-graph",
        "--memory-path",
        "/Users/yourusername/.aim"
      ],
      "env": {}
    }
  }
}

MCP Knowledge Graph tools available to Claude Desktop

MCP Knowledge Graph's stored tool list documents 10 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

aim_memory_store

When Claude Desktop requests aim_memory_store from MCP Knowledge Graph, review the action before approving it.

Create persistent records for people, projects, concepts, or other entities.

aim_memory_link

When Claude Desktop requests aim_memory_link from MCP Knowledge Graph, review the action before approving it.

Connect stored entities using a named directional relationship.

aim_memory_add_facts

When Claude Desktop requests aim_memory_add_facts from MCP Knowledge Graph, review the action before approving it.

Append observations to an existing entity while ignoring duplicates.

aim_memory_forget

When Claude Desktop requests aim_memory_forget from MCP Knowledge Graph, review the action before approving it.

Delete entities together with their associated relationships.

aim_memory_remove_facts

When Claude Desktop requests aim_memory_remove_facts from MCP Knowledge Graph, review the action before approving it.

Remove selected observations without deleting their entity.

aim_memory_unlink

When Claude Desktop requests aim_memory_unlink from MCP Knowledge Graph, review the action before approving it.

aim_memory_read_all

When Claude Desktop requests aim_memory_read_all from MCP Knowledge Graph, review the action before approving it.

aim_memory_search

When Claude Desktop requests aim_memory_search from MCP Knowledge Graph, review the action before approving it.

aim_memory_get

When Claude Desktop requests aim_memory_get from MCP Knowledge Graph, review the action before approving it.

aim_memory_list_stores

When Claude Desktop requests aim_memory_list_stores from MCP Knowledge Graph, review the action before approving it.

MCP Knowledge Graph: full stored tool descriptions

Troubleshooting MCP Knowledge Graph in Claude Desktop

  • Fully quit and reopen Claude Desktop for MCP Knowledge Graph. If npx mcp-knowledge-graph (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • MCP Knowledge Graph uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires Node.js 22 or newer.
  • Known limitation: Project detection depends on the exact .aim directory name.
  • Known limitation: Inconsistent context naming can create redundant databases.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

MCP Knowledge Graph — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads MCP Knowledge Graph from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's mcp-knowledge-graph example uses stdio.

MCP Knowledge Graph's Claude Desktop configuration invokes npx mcp-knowledge-graph (Node.js/npm).

MCP Knowledge Graph's stored list contains 10 tools, including aim_memory_store, aim_memory_link, aim_memory_add_facts. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

The README uses AIM for AI Memory, reflected in tool prefixes, storage directories, and file safety markers.

No. Only project-local automatic detection requires that exact directory name. The configured global path can use another name.