Kuzu Knowledge Graph MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kuzu Knowledge Graph MCP ServerHow does the context graph reduce AI cost and how do I deploy it safely?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kuzu Knowledge Graph MCP Server
A beginner-friendly Model Context Protocol server that connects to an embedded Kuzu graph database and lets AI clients read a knowledge graph.
This project is designed for a first Kuzu journey:
Create a small knowledge graph.
Store it in Kuzu.
Expose read-only graph tools through MCP.
Connect the MCP server to an AI client.
Ask graph-backed questions.
What You Get
TypeScript MCP server over stdio
Embedded Kuzu database connection
Auto-created graph schema
Optional sample data seed
Read-only Cypher guard
Six MCP tools
One schema resource
Dockerfile
Step-by-step docs
Related MCP server: kg-mcp
Why Kuzu
Kuzu is an embedded property graph database. It runs inside your application process, stores graph data on disk, and supports Cypher queries. That makes it a good fit for local or product-embedded knowledge graph workloads where you do not want to run a separate graph database server.
Architecture
AI Client
|
| MCP stdio
v
Kuzu Knowledge Graph MCP Server
|
| Kuzu Node.js API
v
Embedded Kuzu DB directoryRequirements
Node.js 20 or newer
npm, pnpm, or another Node package manager
macOS, Linux, or Windows with a supported Kuzu Node package
Quick Start
git clone <your-repo-url>
cd kuzu-knowledge-graph-mcp
npm install
npm run build
npm run seed
npm run smokeExpected smoke result:
{
"status": "ok",
"nodeCounts": {
"Document": 4,
"Chunk": 8,
"Entity": 8,
"Topic": 4
}
}Run The MCP Server
Development:
npm run devProduction-style:
npm run build
npm run startThe server uses stdio, so it will appear to wait silently. That is normal. MCP clients talk to it through stdin/stdout.
Environment Variables
Copy the example file:
cp .env.example .envImportant settings:
Variable | Default | Meaning |
|
| Directory where Kuzu stores the database |
|
| Create node and relationship tables on startup |
|
| Seed sample data when the database has no documents |
|
| Name shown to MCP clients |
Connect To Claude Desktop Or Another MCP Client
Build first:
npm run buildThen add a config like this to your MCP client. Replace the paths with your real absolute path.
{
"mcpServers": {
"kuzu-knowledge-graph": {
"command": "node",
"args": ["/absolute/path/to/kuzu-knowledge-graph-mcp/dist/src/index.js"],
"env": {
"KUZU_DB_PATH": "/absolute/path/to/kuzu-knowledge-graph-mcp/data/kuzu-demo",
"KUZU_AUTO_CREATE_SCHEMA": "true",
"KUZU_AUTO_SEED": "true"
}
}
}
}An editable copy is available in mcp-config.example.json.
Available MCP Tools
kg_overview: graph counts, topics, and exampleskg_search: keyword search across documents, chunks, entities, and topicskg_get_document_context: document, chunks, topics, and entitieskg_entity_neighborhood: one-hop entity relationships and supporting chunkskg_question_context: compact graph-backed evidence pack for a natural-language questionkg_readonly_cypher: guarded read-only Cypher query
Full tool guide: docs/TOOLS.md
Create And Run A Simple MCP Client
This repo includes a beginner MCP client that starts the Kuzu MCP server, lists tools, reads the schema resource, and calls graph tools.
npm run client:demoClient guide: docs/CLIENT.md
Example Journey
The included sample graph models a GenAI Workbench support and deployment knowledge graph.
Try asking your MCP client:
Use the Kuzu knowledge graph. How does the context graph reduce AI cost and how do I deploy it safely?The expected journey:
Search chunks for context graph, cost, deployment, and safety.
Expand to documents such as
doc-context-costanddoc-deployment.Pull entities like Kuzu, Context Graph, API Key, Tenant Isolation, and REST API.
Return a small evidence pack for the LLM.
Detailed walkthrough: docs/DATA_JOURNEY.md
Useful Read-Only Cypher
MATCH (d:Document)-[:HAS_CHUNK]->(c:Chunk)
RETURN d.title AS document, c.section AS section, c.text AS text
LIMIT 5MATCH (a:Entity)-[r:RELATED_TO]->(b:Entity)
RETURN a.name AS fromEntity, r.relation AS relation, b.name AS toEntity
LIMIT 10More examples: examples/graph-journey.cypher
Deployment
See docs/DEPLOYMENT.md.
Project Structure
src/
index.ts MCP server entrypoint
kuzuGraph.ts Kuzu connection and query wrapper
knowledgeGraphService.ts Graph read operations
schema.ts Kuzu graph schema
seedData.ts Sample data journey
cypher.ts Read-only Cypher validation
scripts/
seed.ts Reset and seed the demo graph
smoke.ts Build confidence test
docs/
DATA_JOURNEY.md
DEPLOYMENT.md
TOOLS.md
examples/
graph-journey.cypher
questions.mdNotes For Beginners
Kuzu is embedded. You are not connecting to a database server URL. You are opening a database directory.
MCP stdio servers do not expose an HTTP port. Your AI client starts the server command and talks through standard input/output.
Do not write normal logs to stdout in an MCP server. stdout is reserved for protocol messages.
Keep raw Cypher read-only unless you are building an admin-only server.
References
Kuzu documentation: https://kuzudb.github.io/docs/
Kuzu Node.js API: https://kuzudb.github.io/docs/client-apis/nodejs/
MCP TypeScript SDK: https://github.com/modelcontextprotocol/typescript-sdk
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SankarPatnaik/kuzu-knowledge-graph-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server