every-db-mcp
Related Servers
Alternatives to every-db-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA unified MCP server for querying and managing multiple database types (PostgreSQL, MySQL, SQL Server, etc.) via natural language through AI assistants.GPL 3.0
- AlicenseAqualityDmaintenanceA multi-database MCP server that enables LLMs to safely interact with MySQL, PostgreSQL, SQLite, and others through a unified tool interface, with permission modes and schema resources.1010 npm65MIT
- AlicenseNot gradedqualityAmaintenanceA multi-database MCP server that enables LLM agents to safely access MySQL, Oracle, DM, PostgreSQL, and SQLite databases with security features like whitelist, row count pre-check, and audit logging.2MIT
- FlicenseNot gradedqualityCmaintenanceMulti-datasource MCP server that connects AI assistants to 6 database types (MySQL, PostgreSQL, ClickHouse, MongoDB, SQLite, Huawei DWS) with dynamic configuration, encrypted credential storage, and schema discovery.-
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that enables database operations, schema management, and statistics via natural language through SQL queries and resources.18 npm-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for SQL Server database operations, enabling CRUD operations, schema exploration, and stored procedure execution through natural language.6 npmMIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: listing databases, testing connections, retrieving table structure, executing SELECT queries, and executing write/DDL operations. There is no overlap, and the descriptions clearly differentiate them.
All tools share the 'db_' prefix and mostly follow a verb_noun pattern (e.g., db_list_databases, db_test_connection). 'db_query' and 'db_execute' are less descriptive but still consistent in using verbs for actions.
Five tools cover the essential database operations (listing, testing, schema inspection, querying, and executing) without being excessive or insufficient. The scope is well-balanced for a database MCP server.
The tool set covers core CRUD and schema operations. Minor gaps exist (e.g., no tool for creating or dropping databases or managing users), but these are reasonable omissions given the focus on read-access and configured databases.