multidb-mcp
Related Servers
Alternatives to multidb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and LLM agents to query operational databases through a read-only MCP gateway with table whitelisting, automatic row limits, sensitive-data masking, and audit logging.1MIT

sql-to-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.3AGPL 3.0- AlicenseNot gradedqualityCmaintenanceProvides a secure, policy-driven read-only gateway that exposes multiple databases to AI tools via MCP, with governed select, search, and aggregate operations and no free-form SQL.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to connect to Microsoft SQL Server through MCP for natural-language querying, schema and table inspection, and running T-SQL with read-only safeguards and multi-environment support.MIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to databases for MCP-compatible AI tools, allowing schema exploration and SELECT queries without exposing credentials or risking data changes.3-
- AlicenseBqualityBmaintenanceEnables Claude, ChatGPT, and other MCP clients to query local files and databases read-only while controlling exactly which rows and columns the AI can see and blocking sensitive tables or columns.55Apache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct step in the database workflow: connection discovery, connectivity testing, table listing, schema inspection, and query execution. The boundaries are clear, and descriptions explicitly guide when to use list_connections versus test_connection.
All tool names follow a consistent snake_case verb_noun pattern: test_connection, list_connections, list_tables, describe_table, execute_sql. The conventions are predictable and readable.
Five tools is well-scoped for a multi-database MCP server, covering discovery, verification, schema introspection, and querying without redundant endpoints. Each tool earns its place.
The surface covers core database access workflows, including connection listing, testing, table discovery, schema description, and SQL execution. Minor gaps exist around listing schemas/databases explicitly or introspecting indexes, but agents can generally work around them.