dsh-databases
Related Servers
Alternatives to dsh-databases
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and modify MySQL and MariaDB databases over MCP, with each connection independently permitting selects, inserts, updates, deletes, and DDL while defaulting to read-only and rejecting anything outside the allowed operations. Connections are configured in JSON, result sets are capped and truncated, and passwords stay server-side.MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and agents to interact with relational databases (SQL Server, MySQL, PostgreSQL) through MCP tools. Supports executing queries, inserting records, listing tables, and exposing database schemas with secure credential management.-
- AlicenseBqualityBmaintenanceEnables agents to connect to and work with PostgreSQL, MySQL, Redis, SQLite, and MongoDB through a uniform tool surface for opening connections, running queries and commands, inspecting schemas, and managing documents.1355 npmMIT
- FlicenseNot gradedqualityBmaintenanceRun SQL against 31 database engines from an agent: list and test saved datasources, execute statements, and page through large result sets. Credentials are stored encrypted and never returned to the caller.3-
- AlicenseBqualityDmaintenanceEnables AI assistants to securely interact with MariaDB and MySQL databases using granular per-connection read/write permissions and transaction support. It allows users to manage multiple database connections, explore schemas, and execute controlled SQL queries through a standardized interface.617 npm5MIT
- AlicenseAqualityBmaintenanceEnables AI agents to query and explore PostgreSQL and MySQL clusters from a single main configuration, with dynamic per-database routing, automatic database discovery and sync, table/schema inspection, and hierarchical write-rule protection that can block or allow specific SQL mutation operations.9MIT
TDQS
Scored across 9 tools
Most tools have clear, distinct purposes split across connection management, discovery, and querying. The main overlap is between test_connection and server_info, which both return version/host/user for the selected connection, making it easy to pick the wrong one for diagnostics.
Nearly all names follow a predictable snake_case verb_noun pattern (list_connections, save_connection, list_tables, describe_table, run_query). The only deviation is the noun-only server_info, which is a minor break in the convention.
Nine tools is well within the sweet spot and each one covers a distinct facet of database exploration and connection management. Nothing feels bloated or missing at the count level.
The surface is read-only: run_query explicitly forbids writes and there is no execute_sql tool, yet save_connection's description tells agents to use execute_sql, a dead reference that will cause failures. For a multi-engine database server, missing any DML/DDL path is a significant lifecycle gap.