Database Query MCP Server
Related Servers
Alternatives to Database Query MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a unified, read-only interface for executing SQL queries across multiple database engines including SQL Server, MySQL, and PostgreSQL via CLI tools. It features automatic project configuration detection and strict query validation to ensure safe AI-driven data interactions.MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants with read-only access to inspect database schemas, preview data, and run safe queries across PostgreSQL, MySQL, MongoDB, and SQL Server. It enables AI tools to understand database structures and relationships automatically to generate more accurate code.15 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables running single, validated SELECT statements against PostgreSQL, MySQL/MariaDB, SQL Server, SQLite, and Oracle through read-only sessions with schema/table inspection, query plans, row limits, timeouts, and an audit log. Keeps the assistant strictly read-only by combining a read-only database user, SQL validation, and automatic rollback.MIT
- FlicenseAqualityDmaintenanceEnables read-only exploration of a Postgres database using natural language, with multiple safety layers to prevent any modifications.5-
- AlicenseNot gradedqualityDmaintenanceEnables secure, read-only PostgreSQL database interaction through natural language, with automatic database discovery and connection management.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query relational databases like MySQL, PostgreSQL, and Oracle using natural-language questions, dynamically discovering schemas and generating validated read-only SQL through configurable AI providers such as Groq, Claude, and Gemini.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose targeting a specific database system (MSSQL, MySQL, Oracle, PostgreSQL). There is no ambiguity or overlap since each tool is dedicated to a different database technology, making tool selection straightforward for agents based on the target system.
All tool names follow a perfectly consistent verb_noun pattern: 'query_' followed by the database name (e.g., query_mssql, query_mysql). This uniform naming convention makes the tools predictable and easy to understand, with no deviations in style or structure.
With 4 tools, the count is reasonable for a database query server covering multiple systems. It might be slightly thin if additional database types (e.g., SQLite) are expected, but it effectively covers major databases without being overwhelming, making it well-scoped for its purpose.
The server provides read-only query capabilities for multiple databases, which is a clear and focused domain. However, there are notable gaps: it lacks write operations (e.g., insert, update, delete) and administrative functions (e.g., schema management, connection testing), limiting agents to read-only workflows and potentially causing failures for broader database tasks.