Kuzu MCP server implementation
Kuzu MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Kuzu MCP server implementation.
A Model Context Protocol server that provides access to Kuzu databases. This server enables LLMs to inspect database schemas and execute queries on provided kuzu database.
Once Kuzu is connected, these are the calls the assistant has available:
getSchema — Fetch the full schema of the Kuzu database, including all nodes and relationships tables and their propertiesInput — Nonequery — Run a Cypher query on the Kuzu databaseTools — The Tools tool exposed by this serverPrompt — The Prompt tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Kuzu's toolset — getSchema, Input, query and 2 more — is a fair guide to whether it matches your workflow. It is maintained by kuzudb; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| getSchema | Fetch the full schema of the Kuzu database, including all nodes and relationships tables and their properties |
| Input | None |
| query | Run a Cypher query on the Kuzu database |
| Tools | The Tools tool exposed by this server. |
| Prompt | The Prompt tool exposed by this server. |
{
"mcpServers": {
"kuzu": {
"command": "docker",
"args": [
"run",
"-v",
"{Path to the directory containing Kuzu database file}:/database",
"-e",
"KUZU_DB_FILE={Kuzu database file name}",
"--rm",
"-i",
"kuzudb/mcp-server"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.