MCP Knowledge Graph Alternatives: 3 MCP Servers

Keep assistant memories as local entities, relationships, and facts across conversations. MCP Knowledge Graph supports project-specific and global JSONL stores, optional topic databases, and explicit memory editing tools.

MCP Knowledge Graph alternatives compared

MCP Knowledge Graph gives assistants persistent memory built from entities, relationships, and observations. A memory can represent a person, project, or concept, while links connect those records and facts extend their descriptions. Tools support creating, retrieving, searching, and removing this information across conversations. The README presents the system for Claude Code, Claude Desktop, and other MCP-compatible platforms rather than tying the storage format to one assistant application.

Ranked by shared tags × quality; ties: quality, non-monorepo stars, slug.

MCP Knowledge Graph setup notes

MCP Knowledge Graph's stdio example needs a client that launches local processes.

Why switch from MCP Knowledge Graph

1. Basic Memory

MCP Knowledge Graph and Basic Memory have no exact tool-name overlap in their recorded lists. Basic Memory lists 7 names absent from MCP Knowledge Graph, including edit_note, fetch, schema_diff. Moving from MCP Knowledge Graph to Basic Memory would also mean rechecking workflows using aim_memory_add_facts, aim_memory_forget, aim_memory_get, which appear only in MCP Knowledge Graph's list. MCP Knowledge Graph records node; Basic Memory records python. MCP Knowledge Graph and Basic Memory both list stdio. MCP Knowledge Graph is listed under MIT, versus AGPL-3.0 for Basic Memory. Basic Memory's repository has 3,378 more stars than MCP Knowledge Graph (4,263 versus 885). Last pushes: MCP Knowledge Graph 2026-05-29; Basic Memory 2026-10-16.

Basic Memory overlaps MCP Knowledge Graph on: knowledge-graph.

2. Context Portal MCP (ConPort)

MCP Knowledge Graph and Context Portal MCP (ConPort) have no exact tool-name overlap in their recorded lists. Context Portal MCP (ConPort) lists 1 name absent from MCP Knowledge Graph, including get_conport_schema. Moving from MCP Knowledge Graph to Context Portal MCP (ConPort) would also mean rechecking workflows using aim_memory_add_facts, aim_memory_forget, aim_memory_get, which appear only in MCP Knowledge Graph's list. MCP Knowledge Graph records node; Context Portal MCP (ConPort) records python. MCP Knowledge Graph and Context Portal MCP (ConPort) both list stdio. MCP Knowledge Graph is listed under MIT, versus Apache-2.0 for Context Portal MCP (ConPort). Context Portal MCP (ConPort)'s repository has 118 fewer stars than MCP Knowledge Graph (767 versus 885). Last pushes: MCP Knowledge Graph 2026-05-29; Context Portal MCP (ConPort) 2026-01-27.

Context Portal MCP (ConPort) overlaps MCP Knowledge Graph on: knowledge-graph.

3. Memory Bank MCP Server

MCP Knowledge Graph and Memory Bank MCP Server have no exact tool-name overlap in their recorded lists. Memory Bank MCP Server lists 5 names absent from MCP Knowledge Graph, including list_project_files, list_projects, memory_bank_read. Moving from MCP Knowledge Graph to Memory Bank MCP Server would also mean rechecking workflows using aim_memory_add_facts, aim_memory_forget, aim_memory_get, which appear only in MCP Knowledge Graph's list. MCP Knowledge Graph and Memory Bank MCP Server both list node / stdio / MIT. Memory Bank MCP Server's repository has 36 more stars than MCP Knowledge Graph (921 versus 885). Last pushes: MCP Knowledge Graph 2026-05-29; Memory Bank MCP Server 2025-08-20.

Memory Bank MCP Server overlaps MCP Knowledge Graph on: project-context.