GraphMemory-IDE: AI-Powered Collaborative Memory Platform
@elementalcollision
About GraphMemory-IDE: AI-Powered Collaborative Memory Platform
AI-assisted development MCP providing long-term, on-device "AI memory" for IDEs. Powered by Kuzu GraphDB and exposed via MCP server
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"GraphMemory-IDE": {
"command": "docker",
"args": [
"compose",
"up",
"-d"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is GraphMemory-IDE?
GraphMemory-IDE is an AI-assisted, long-term memory MCP (Model Context Protocol) server for IDEs, powered by the Kuzu graph database. It provides semantic vector search, graph-based knowledge storage, and real-time analytics, integrating with VSCode, Cursor, and Windsurf through dedicated plugins.
How to use GraphMemory-IDE?
Deploy with Docker (recommended): clone the repository, navigate to docker/, and run docker compose up -d. For local development, install dependencies with pip install -r requirements.txt, start the FastAPI server with uvicorn server.main:app --host 0.0.0.0 --port 8080 --reload, and optionally launch the Streamlit dashboard separately. Required environment variables include JWT_SECRET_KEY, DATABASE_URL, REDIS_URL, and KUZU_DB_PATH.
Key features of GraphMemory-IDE
- Graph-based memory storage with Kuzu and HNSW vector indexes
- Codon-accelerated graph algorithms with 10–100x speedups
- FastAPI backend with JWT authentication and rate limiting
- Real-time analytics via WebSocket and SSE streaming
- Multi-IDE plugin support (VSCode, Cursor, Windsurf)
- Production-ready Docker deployment with monitoring stack
Use cases of GraphMemory-IDE
- Persistent, retrievable memory for AI-assisted coding sessions
- Collaborative knowledge sharing across development teams
- Real-time telemetry and analytics for IDE usage patterns
- Semantic search over code artifacts and project context
FAQ from GraphMemory-IDE
What is GraphMemory-IDE and how is it different from other memory systems?
GraphMemory-IDE is a dedicated MCP server that combines a Kuzu graph database with semantic vector search, optional Codon-accelerated graph algorithms, and real-time analytics dashboards. It is designed specifically for IDE integration and offers multi-plugin support out of the box.
What are the runtime requirements?
Python 3.11 or higher, with dependencies in requirements.txt. Codon is optional but recommended for high-performance graph algorithms; if not compiled, all operations fall back to NetworkX and numpy. Docker Compose is available for production deployment with PostgreSQL, Redis, Prometheus, and Grafana.
Where is data stored?
Graph data is stored in a Kuzu database at the path specified by KUZU_DB_PATH (default ./data/kuzu). Relational data and sessions are stored in PostgreSQL (default SQLite) and Redis cache respectively.
Does GraphMemory-IDE support authentication?
Yes, the FastAPI server uses JWT authentication with EdDSA/Ed25519 signing. A JWT_SECRET_KEY environment variable must be configured.
What are the known limitations?
Codon acceleration requires manual compilation of native libraries via ./scripts/build_codon.sh and is only beneficial for graphs larger than 100 nodes (configurable). The system is designed for IDE-integrated use; direct API access is available but intended for plugin and dashboard communication.
Frequently asked questions
What is GraphMemory-IDE and how is it different from other memory systems?
GraphMemory-IDE is a dedicated MCP server that combines a Kuzu graph database with semantic vector search, optional Codon-accelerated graph algorithms, and real-time analytics dashboards. It is designed specifically for IDE integration and offers multi-plugin support out of the box.
What are the runtime requirements?
Python 3.11 or higher, with dependencies in `requirements.txt`. Codon is optional but recommended for high-performance graph algorithms; if not compiled, all operations fall back to NetworkX and numpy. Docker Compose is available for production deployment with PostgreSQL, Redis, Prometheus, and Grafana.
Where is data stored?
Graph data is stored in a Kuzu database at the path specified by `KUZU_DB_PATH` (default `./data/kuzu`). Relational data and sessions are stored in PostgreSQL (default SQLite) and Redis cache respectively.
Does GraphMemory-IDE support authentication?
Yes, the FastAPI server uses JWT authentication with EdDSA/Ed25519 signing. A `JWT_SECRET_KEY` environment variable must be configured.
What are the known limitations?
Codon acceleration requires manual compilation of native libraries via `./scripts/build_codon.sh` and is only beneficial for graphs larger than 100 nodes (configurable). The system is designed for IDE-integrated use; direct API access is available but intended for plugin and dashboard communication.
Basic information
More Developer Tools MCP servers
endoflife.ai
endoflife.aiFree MCP server for software end-of-life intelligence: EOL dates, support status, and the 0-100 EOL Risk Score across 485 tracked products. Agents can check a single version, pull a product's full lifecycle schedule, or
Vibgrate MCP
VibgrateQuery your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
MCP Unity Editor (Game Engine)
CoderGamesterModel Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs
Altronis
sypherinMCP server + CLI for Altronis — Singapore AI consulting. Ask the Lyra consultant, generate a grant-matched AI transformation plan, pull curated SG AI events/news. Read-only, wraps altronis.sg.
Comments