Geniro Graphiti MCP
A Model Context Protocol server that provides Claude CLI with a Graphiti knowledge-graph memory backed by Neo4j, featuring synchronous writes and no silent ingestion failures.
README
Geniro Graphiti MCP
A clean-room Model Context Protocol server that gives the Claude CLI a Graphiti knowledge-graph memory, backed by Neo4j.
It embeds graphiti-core in-process and writes synchronously: add_memory
awaits the actual graph write and returns the real result. There is no background
queue, so an ingestion failure is reported to you immediately instead of being
silently dropped while the tool reports success — the bug that affects the
upstream server and its forks.
Why this exists
The upstream Graphiti MCP server enqueues each episode on an in-memory
asyncio.Queue and returns success right away. If processing fails, the error is
only logged; if the process restarts, the whole queue is lost. You get "success"
and an empty graph. This rewrite removes the queue entirely:
- Synchronous awaited writes — errors propagate to the caller.
- Two-model config done right — a main LLM and an embedder are both required and validated; a misconfigured embedder fails loudly instead of silently returning no search results.
- A real test suite — unit tests prove the no-silent-drop guarantee; testcontainers integration tests run against a real Neo4j.
Requirements
- Python 3.11+
- A running Neo4j 5.26+ (use the bundled
docker-compose.yml) - An LLM provider key (OpenAI by default) and a reachable embedder
uv(recommended) orpip/pipx- Docker (only for the integration tests / bundled Neo4j)
Quick start
# 1. Start Neo4j
docker compose up -d
# 2. Configure
cp .env.example .env
# edit .env: set OPENAI_API_KEY, and point the embedder at a real embedding model
# 3. Install
uv sync # or: pip install .
# 4. Run (stdio)
uv run graphiti-mcp # or just: graphiti-mcp
Register with the Claude CLI
claude mcp add graphiti-mcp -- graphiti-mcp
If you installed into a virtualenv, point Claude at the resolved binary, e.g.:
claude mcp add graphiti-mcp -- uv run --directory /path/to/geniro-graphiti-mcp graphiti-mcp
Then, from Claude: call add_memory, then search_memory_facts, and confirm the
fact comes back; get_status reports Neo4j connectivity and the resolved providers.
Configuration
All configuration is via environment variables (or .env). See
.env.example for the full list. Highlights:
| Variable | Default | Notes |
|---|---|---|
NEO4J_URI |
bolt://localhost:7687 |
Bolt endpoint |
NEO4J_USER / NEO4J_PASSWORD |
neo4j / demodemo |
Match docker-compose.yml |
LLM_PROVIDER |
openai |
openai | anthropic | openai_generic |
LLM_MODEL |
gpt-5.5 |
Extraction model |
LLM_BASE_URL |
— | Required for openai_generic (LiteLLM/Ollama/vLLM) |
EMBEDDER_PROVIDER |
ollama |
openai | ollama | voyage | openai_generic |
EMBEDDER_MODEL |
qwen3-embedding:8b |
Must be an embedding model |
EMBEDDER_DIM |
4096 |
Must match the model's output dimension |
EMBEDDER_BASE_URL |
http://localhost:11434/v1 |
Ollama default |
GRAPHITI_GROUP_ID |
main |
Optional memory namespace |
Provider notes
- Two models are always needed. An LLM extracts entities/relationships; an embedder vectorizes them for search. Configuring only an LLM yields empty search results.
- OpenAI-compatible endpoints (LiteLLM, Ollama, vLLM, OpenRouter) must use
LLM_PROVIDER=openai_generic. This uses graphiti-core'sOpenAIGenericClientsoLLM_BASE_URLis honoured — the nativeOpenAIClientignoresbase_url(graphiti issue #1116) and would silently hit api.openai.com. - Anthropic / Voyage need optional extras:
uv pip install '.[anthropic]'or'.[voyage]'. - Embedding model, not chat model.
qwen3-embedding:8bis an embedding model;qwen3:8bis a chat model and will break search.EMBEDDER_DIMmust match.
Tools
| Tool | Purpose |
|---|---|
add_memory |
Ingest an episode (synchronous, awaited). |
add_triplet |
Add an explicit (source)-[edge]->(target) fact. |
search_memory_facts |
Search relationships (facts). |
search_nodes |
Search entity nodes. |
get_episodes |
List recent episodes. |
get_episode_entities |
Entities extracted from an episode. |
get_entity_edge |
Fetch one edge by UUID. |
delete_entity_edge |
Delete an edge by UUID. |
delete_episode |
Delete an episode by UUID. |
build_communities |
(Re)build community clusters. |
summarize_saga |
Summarize a thread of episodes. |
clear_graph |
Delete all data for one group (destructive, group-scoped). |
get_status |
Neo4j connectivity + resolved providers. |
Testing
# Unit tests (mocked graphiti-core — no Neo4j needed)
uv run pytest tests/unit -q
# Integration tests (spins a real Neo4j via testcontainers; needs Docker + an
# embedder/LLM the container can reach)
uv run pytest -m integration -q
# Everything
uv run pytest -q
The unit suite includes the core guarantee: when a write fails, add_memory
returns an error synchronously — never a false success.
Architecture
Claude CLI ──stdio──> graphiti-mcp (FastMCP)
│
├─ config.py env/.env settings
├─ providers.py LLM + embedder factories
├─ engine.py Graphiti(Neo4jDriver, llm, embedder)
├─ tools/ the 13 MCP tools (await writes)
└─ models.py pydantic responses
│
└─ graphiti-core ──Bolt──> Neo4j
The engine is embedded directly (architecture A) — no separate Graphiti REST service, no network hop, no async-202 durability bug.
License
Apache-2.0.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.