mcp-server-db
Related Servers
Alternatives to mcp-server-db
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
- AlicenseNot gradedqualityNot gradedmaintenanceA universal database gateway MCP server that enables AI assistants to connect to and query multiple databases (PostgreSQL, MySQL, MariaDB, SQL Server, SQLite) with support for schema exploration, SQL execution, and secure connections via SSH tunnels.3 npm-
- AlicenseNot gradedqualityDmaintenanceZero-config MCP server that empowers AI agents to safely query SQL and NoSQL databases like PostgreSQL, MySQL, SQLite, MongoDB, and Redis.9 npm1MIT
- 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 gradedqualityDmaintenanceUniversal Database MCP Server enabling AI assistants to connect and query multiple databases including Databricks, BigQuery, PostgreSQL, MySQL, SQL Server, SQLite, and MariaDB through a unified interface.22 npmMIT
- 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.-
TDQS
Scored across 113 tools
Engine prefixes and resource-specific predicates clearly separate tools, e.g., pg_list_tables vs redis_hgetall vs mongo_find. Minor overlap exists among PostgreSQL statistics and index analysis tools (pg_table_stats vs pg_sizes_overview vs pg_database_health), but descriptions generally differentiate them.
The overwhelming majority follow a consistent engine_verb_noun snake_case pattern, such as pg_list_tables, redis_hset, mongo_insert_one, and es_delete_doc. Exceptions like db_status (no verb) and the variation between es_bulk_index and ldap_add_bulk are minor deviations from an otherwise strong convention.
At 113 tools, the surface is far beyond the typical 3-15 tool scope and overwhelms agents even though the server spans multiple database engines. The sheer number exceeds the 'too many' threshold, and the breadth would be better split into dedicated per-engine MCP servers.
CRUD, schema inspection, query execution, and administrative operations are thoroughly covered for PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, and LDAP. Notable gaps include Redis sorted-set operations, Elasticsearch index creation/deletion, and Mongo drop collection/database, but these are minor relative to the very broad surface.