Kuzu MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUZU_READ_ONLY | No | If set to 'true', prevents any queries that modify the database from being executed | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryC | Run a Cypher query on the Kuzu database |
| getSchemaB | Get the schema of the Kuzu database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generateKuzuCypher | Generate a Cypher query for Kuzu |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: getSchema retrieves database structure metadata, while query executes data retrieval/manipulation operations. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
Both tools follow a consistent verb_noun naming pattern (getSchema, query). While 'query' is a noun rather than verb_noun, it's a standard database term that pairs naturally with 'getSchema', maintaining clear and predictable naming throughout the minimal toolset.
With only 2 tools, this server feels severely under-scoped for a database interface. A typical database MCP server would include tools for data manipulation (insert, update, delete), transaction management, connection handling, or at least parameterized queries beyond just raw query execution.
For a database server, the surface is significantly incomplete. While getSchema and query provide read capabilities, there are no tools for data modification (insert/update/delete), transaction control, connection management, or even parameterized query execution. This creates dead ends for agents needing to perform basic database operations.