MCP Knowledge Graph for Cursor: Setup & Config

What you can do with MCP Knowledge Graph in Cursor

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

• Keep repository-specific memory in a project's .aim directory.
• Look up known entities or search observations by keyword.

Before you start: MCP Knowledge Graph in Cursor

• 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 Cursor configuration

1. Choose Cursor configuration scope

   For MCP Knowledge Graph, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add MCP Knowledge Graph to Cursor

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

3. Check MCP Knowledge Graph in Cursor

   MCP Knowledge Graph: Enable in Cursor’s MCP settings; inspect tools.

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

MCP Knowledge Graph tools available to Cursor

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

aim_memory_store

Find aim_memory_store under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

aim_memory_link

Find aim_memory_link under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

aim_memory_add_facts

Find aim_memory_add_facts under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

aim_memory_forget

Find aim_memory_forget under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

aim_memory_remove_facts

Find aim_memory_remove_facts under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

aim_memory_unlink

Find aim_memory_unlink under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Remove relationships while preserving the linked entities.

aim_memory_read_all

Find aim_memory_read_all under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Read a database's complete graph as structured JSON or readable text.

aim_memory_search

Find aim_memory_search under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Match keywords against entity names, types, and observations without case sensitivity.

aim_memory_get

Find aim_memory_get under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Retrieve entities by exact name and include relationships between the selected records.

aim_memory_list_stores

Find aim_memory_list_stores under MCP Knowledge Graph in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Discover project and global databases and report the current storage location.

MCP Knowledge Graph: full stored tool descriptions

Troubleshooting MCP Knowledge Graph in Cursor

• Cursor must find npx mcp-knowledge-graph (Node.js/npm) for MCP Knowledge Graph. Enable the project/user entry in MCP settings and inspect its tools.
• MCP Knowledge Graph uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions