mcp-knowledge-graph MCP Server
shaneholloman/mcp-knowledge-graph
[](https://agentrank-ai.com/tool/shaneholloman--mcp-knowledge-graph/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
shaneholloman/mcp-knowledge-graph is a JavaScript MCP server licensed under MIT. MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development Topics: ai-memory, claude-ai, knowledge-graph, mcp, memory-server, typescript.
Ranked #14822 out of 24846 indexed tools.
Ecosystem
Score Breakdown
888 stars → growing community
Last commit 5mo ago → stale
17/20 issues closed → responsive maintainer
1 contributor → solo project
2 dependents → few downstream users
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
How to Improve
Matched Queries
From the README
# MCP Knowledge Graph
**Persistent memory for AI models through a local knowledge graph.**
Store and retrieve information across conversations using entities, relations, and observations. Works with Claude Code/Desktop and any MCP-compatible AI platform.
## Why ".aim" and "aim_" prefixes?
AIM stands for **AI Memory** - the core concept of this system. The three AIM elements provide clear organization and safety:
- **`.aim` directories**: Keep AI memory files organized and easily identifiable
- **`aim_` tool prefixes**: Group related memory functions together in multi-tool setups
- **`_aim` safety markers**: Each memory file starts with `{"type":"_aim","source":"mcp-knowledge-graph"}` to prevent accidental overwrites of unrelated JSONL files
This consistent AIM naming makes it obvious which directories, tools, and files belong to the AI memory system.
## CRITICAL: Understanding `.aim` dir vs `_aim` file marker
**Two different things with similar names:**
- `.aim` = **Project-lo Read full README on GitHub → Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.