Kuzu MCP server
OfficialRelated Servers
Alternatives to Kuzu MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceA 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.17 npm8MIT
- AlicenseBqualityFmaintenanceThis server enables interaction between Neo4j databases and Claude Desktop, allowing users to execute Cypher queries, create nodes, and establish relationships in the database.383 npm59MIT
- FlicenseNot gradedqualityDmaintenanceA server that enables interaction with PostgreSQL, MySQL, MariaDB, or SQLite databases through Claude Desktop using natural language queries.1-
- AlicenseNot gradedqualityDmaintenanceThis server enables Claude to directly interact with SQLite, SQL Server, PostgreSQL, and MySQL databases through the Model Context Protocol, allowing for query execution, table management, and data export capabilities.MIT
- AlicenseNot gradedqualityDmaintenanceA persistent memory server that implements a local knowledge graph using the Kuzu embedded database to store entities, relationships, and observations. It enables AI models to maintain structured long-term context through searchable nodes and comprehensive tag-based organization.8 npmMIT
- AlicenseCqualityAmaintenanceA server that enables LLMs (like Claude and VSCode Copilot) to interact with Azure Cosmos DB data through natural language queries, acting as a translator between AI assistants and your database.311 npm3MIT
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.