Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Persistent knowledge-graph memory for AI agents, with local semantic search. No API keys.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GRAPHMEM_DB_PATH, GRAPHMEM_EMBEDDING_MODEL, GRAPHMEM_TRAVERSAL_NODE_BUDGET, GRAPHMEM_LOG_LEVELYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"graphmem": {
"command": "uvx",
"args": [
"graphmem-mcp"
],
"env": {
"GRAPHMEM_DB_PATH": "your-value",
"GRAPHMEM_EMBEDDING_MODEL": "your-value",
"GRAPHMEM_TRAVERSAL_NODE_BUDGET": "your-value",
"GRAPHMEM_LOG_LEVEL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add graphmem --env GRAPHMEM_DB_PATH=your-value --env GRAPHMEM_EMBEDDING_MODEL=your-value --env GRAPHMEM_TRAVERSAL_NODE_BUDGET=your-value --env GRAPHMEM_LOG_LEVEL=your-value -- uvx graphmem-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"graphmem": {
"command": "uvx",
"args": [
"graphmem-mcp"
],
"env": {
"GRAPHMEM_DB_PATH": "your-value",
"GRAPHMEM_EMBEDDING_MODEL": "your-value",
"GRAPHMEM_TRAVERSAL_NODE_BUDGET": "your-value",
"GRAPHMEM_LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"graphmem": {
"type": "stdio",
"command": "uvx",
"args": [
"graphmem-mcp"
],
"env": {
"GRAPHMEM_DB_PATH": "your-value",
"GRAPHMEM_EMBEDDING_MODEL": "your-value",
"GRAPHMEM_TRAVERSAL_NODE_BUDGET": "your-value",
"GRAPHMEM_LOG_LEVEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GRAPHMEM_DB_PATH envGRAPHMEM_EMBEDDING_MODEL envGRAPHMEM_TRAVERSAL_NODE_BUDGET envGRAPHMEM_LOG_LEVEL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Sathvik-1007, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Persistent knowledge graph memory for AI agents and IDEs
Graph-Mem MCP is a universal MCP server that gives any agent or IDE persistent, structured memory through a knowledge graph. It combines graph storage, semantic vector search, and multi-hop traversal in a single package — install it, add it to your MCP config, and your agent gains memory that survives across sessions. It works everywhere MCP does.
| 1055 tests | Property-based against a brute-force reference, plus fuzzing on every parser |
| mypy strict | Clean, enforced in CI — not just configured |
| Authenticated UI | Host + Origin allow-lists and a session token; a cross-origin write is a 403, verified against a running server |
| Bounded | Every traversal, search, and list response has a named, configurable cap and reports truncation |
| Honest docs | Performance claims come with measurements and a reproducible benchmark; known gaps are written down |
graph-mem is a standard MCP server, so it works with any MCP-compatible agent, IDE, or framework. graph-mem install additionally writes the skill file straight into the right place for these 13, each at a path cited against the vendor's own documentation:
Claude Code OpenCode Cursor Windsurf Codex CLI
Gemini CLI GitHub Copilot Amp Kiro Roo Code
Continue Antigravity Droid (Factory) add yours →
Using something else? The MCP config below is all you need; the skill file is a convenience, not a requirement. Adding your agent to the installer takes a documented path and about ten lines — see Adding an Agent.
AI agents forget everything between sessions. They re-read files, re-discover architecture, and repeat mistakes. Graph-Mem MCP solves this by providing persistent, per-project knowledge graphs that any MCP-compatible agent can read and write to. The graph builds organically as the agent works — extracting entities, decisions, and relationships from every conversation. It runs as a standard MCP server with 28 tools that plug into any agent, IDE, or framework that supports the Model Context Protocol.
Vector search finds _similar_ things. Graphs find _connected_ things. When an agent asks "what depends on the auth service?", a vector store returns text that mentions auth. A knowledge graph traverses the actual dependency edges and returns every upstream consumer — even ones that never mention "auth" in their description. Graph-Mem gives you both: vector similarity for fuzzy discovery, graph traversal for structural queries.
1. Install:
pip install graphmem-mcp
Or run it without installing — uvx fetches and isolates it the way npx does for Node:
uvx --from graphmem-mcp graph-mem server
Listed in the official MCP Registry as io.github.Sathvik-1007/graphmem-mcp, so MCP-aware clients can discover and install it directly.
2. Install the skill for your agent:
graph-mem install claude # Claude Code
graph-mem install opencode # OpenCode graph-mem install codex # Codex CLI graph-mem install gemini # Gemini CLI graph-mem install cursor # Cursor graph-mem install windsurf # Windsurf graph-mem install amp # Amp graph-mem install antigravity # Antigravity graph-mem install copilot # GitHub Copilot graph-mem install kiro # Kiro graph-mem install roocode # Roo Code graph-mem install continue # Continue graph-mem install droid # Droid (Factory)
This writes a skill file that teaches your agent how to use all 28 MCP tools — when to search, when to add entities, naming conventions, and common workflows.
3. Configure MCP by adding this to your agent's MCP config:
{
"mcpServers": { "graph-mem": { "command": "graph-mem", "args": ["server"] } } }
With full customization:
{
"mcpServers": { "graph-mem": { "command": "graph-mem", "args": [ "server", "--project-dir", "/path/to/my/project", "--embedding-model", "sentence-transformers/all-mpnet-base-v2", "--use-onnx", "--cache-size", "20000", "--log-level", "INFO" ] } } }
That's it. Your agent now has persistent memory. Verify by asking it to run read_graph().
Paste this into your agent's chat to get started immediately:
I want you to give yourself persistent memory using graph-mem. Run the following:
pip install graphmem-mcp graph-mem install claude # or: opencode, codex, gemini, cursor, windsurf, amp,
This installs a skill file that teaches you how to use all 28 MCP tools. The server should already be configured in your MCP config. If not, add it:
{ "mcpServers": { "graph-mem": { "command": "graph-mem", "args": ["server", "--project-dir", "/path/to/your/project"] } } }
Now start using the knowledge graph:
Your goal: build a rich knowledge graph of this project so future sessions start with full context instead of from zero. Search before adding to avoid duplicates. Be specific with entity names and types.
pip install graphmem-mcp
graph-mem server
uvx --from graphmem-mcp graph-mem server
uvx downloads the package into an isolated environment and runs it in one command. Nothing to pre-install beyond uv.
git clone https://github.com/Sathvik-1007/GraphMem-MCP
cd graph-mem pip install -e ".[full,dev]" graph-mem server
pip install "graphmem-mcp[embeddings]" # sentence-transformers for local embeddings
pip install "graphmem-mcp[onnx]" # ONNX runtime for embedding inference pip install "graphmem-mcp[ui]" # aiohttp for interactive graph visualisation pip install "graphmem-mcp[full]" # all of the above
Graph-Mem exposes 28 MCP tools — ten for writing, nine for reading, four for maintenance, four for multi-graph management, and one utility. Full CRUD on every primitive: entities, relationships, and observations can all be created, read, updated, and deleted.
| Tool | Description |
|---|---|
add_entities | Batch-create entities with optional observations; auto-merges on name conflict; returns quality screening hints |
add_relationships | Create typed, directed edges between entities; merges duplicates by max weight |
add_observations | Attach factual statements to entities with optional source provenance |
update_entity | Modify entity name, description, properties, or type in-place (rename with collision check) |
update_relationship | Change weight, type, or properties of an existing edge without delete+re-create |
update_observation | Edit observation text content in-place with automatic embedding recompute |
delete_entities | Remove entities with cascade to relationships, observations, and embeddings |
delete_relationships | Remove specific edges between entities, optionally filtered by type |
delete_observations | Remove specific observations by ID with ownership validation |
merge_entities | Combine duplicate entities: moves observations and relationships, deduplicates edges |
| Tool | Description |
|---|---|
search_nodes | Hybrid semantic + full-text search with RRF fusion ranking |
search_observations | Semantic search directly over observation text content |
find_connections | Multi-hop BFS graph traversal with direction and type filters |
get_entity | Full entity details with all observations and relationships |
list_entities | Browse/paginate all entities with optional type filter |
list_relationships | Browse/paginate relationships with entity, type, or combined filters |
read_graph | Graph statistics: counts, type distributions, most-connected entities |
get_subgraph | Extract neighborhood subgraph around seed entities |
find_paths | Find shortest paths between two entities via BFS |
| Tool | Description |
|---|---|
graph_health | Health stats: counts, hotspots, missing descriptions, suggested actions |
compact_observations | Atomic observation compaction — delete old and add merged summaries in one step |
suggest_connections | Find semantically similar entities for a node to connect to |
audit_graph | Full quality screening — disconnected nodes, missing data, weak links. Returns structured findings plus a rendered report field |
| Tool | Description |
|---|---|
open_dashboard | Launch interactive graph visualisation UI and return its URL |
| Tool | Description |
|---|---|
list_graphs | List all named graphs in the .graphmem/ directory with entity/relationship/observation counts |
create_graph | Create a new named graph (.graphmem/ .db) |
switch_graph | Switch the active graph — hot-swaps storage, search, and graph engines |
delete_graph | Delete a named graph (cannot delete the currently active graph) |
Multi-graph storage: Each named graph is a separate SQLite database in
.graphmem/. The default graph isgraph.db. Use--graphon CLI commands to target a specific graph.
graph TD
Agent[Any MCP-Compatible Agent or IDE] --> Transport
subgraph Transport STDIO[stdio] SSE[SSE] HTTP[streamable-http] end
Transport --> Tools
subgraph Tools[Graph-Mem MCP Server — 28 MCP Tools] Write[Write · 10 tools] Read[Read · 9 tools] Maint[Maintenance · 4 tools] Graph[Multi-Graph · 4 to
Only the beginning is shown; read the rest in the repo