About Graphiti
Graphiti is an MCP server published by rawr-ai in the AI category: graphiti Model Context Protocol (MCP) Server - An MCP server for knowledge graph management via Graphiti.
The repository has 102 stars and 21 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/rawr-ai/mcp-graphitiThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Graphiti
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
1 check has not been run yet.
README
Graphiti MCP Server
Fork of the getzep/graphiti example with a focus on developer experience and multi‑project support. Graphiti extracts entities and relationships from text and stores them in Neo4j. This repo adds a CLI that spins up a root server plus project‑specific MCP servers in Docker so several knowledge graphs share the same database.
Quick Start
- Install and clone
pipx install 'git+https://github.com/rawr-ai/mcp-graphiti.git' git clone https://github.com/rawr-ai/mcp-graphiti.git cd mcp-graphiti cp .env.example .env # fill in Neo4j credentials and your OpenAI key - Launch services
The root server runs on port 8000; project containers start at 8001.graphiti compose # generates docker-compose.yml and updates .cursor/mcp.json graphiti up -d - Create a project
Reruncd /path/to/my-kg graphiti init my-kg # writes ai/graph/mcp-config.yaml # add entity definitions under ai/graph/entities/graphiti compose && graphiti up -dfrom anywhere to start its container.
Once running you can:
- Check
http://localhost:8000/graphiti/status. - Connect MCP‑compatible tools to
http://localhost:800{N}/sse. - Browse Neo4j at
http://localhost:7474using the credentials in.env.
Security note
If NEO4J_PASSWORD remains password the server refuses to start unless GRAPHITI_ENV=dev. Always use a strong password in production.
Why this fork?
The upstream repository assumes one server per compose file. Here a single compose file manages many project servers that share Neo4j. Each service gets its own group_id, entities and model so projects stay isolated while running on the same database.
Highlights
- Project isolation – different extraction rules or models never collide.
- Editor auto‑discovery – ports are written to
.cursor/mcp.json. - Crash containment – a bad prompt only restarts its container.
- Hot reload – tweak a project's config and run
graphiti reload <container>.
Leave mcp-projects.yaml empty if you only need the root server.
Danger zone
Setting NEO4J_DESTROY_ENTIRE_GRAPH=true wipes all projects the next time you run graphiti up. Use with care.
Contributing
PRs and issues are welcome.
© 2025 rawr‑ai • MIT License
README fetched from the repository 5 days ago. The original is authoritative.