simple-db-mcp
Related Servers
Alternatives to simple-db-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Python MCP server that enables schema discovery, read-only SQL queries, table previews, and index/relationship analysis on PostgreSQL databases.1MIT
- AlicenseNot gradedqualityCmaintenanceA Python MCP server for inspecting and querying MySQL databases, providing table discovery, schema inspection, read-only queries, and optional write/DDL tools.MIT
- AlicenseAqualityCmaintenanceMCP server for querying and managing multiple databases (SQLite, PostgreSQL, MySQL) with read-only mode and schema inspection.13MIT
- AlicenseNot gradedqualityCmaintenanceA cross-platform MCP server for querying and introspecting PostgreSQL databases with SSH tunnel support, featuring multi-layered query safety and read-only enforcement.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for safe read-only PostgreSQL exploration and querying, enforced by three independent layers: startup privilege audit, lexical guard, and read-only transactions. Offers tools for querying, table listing, schema description, relationship mapping, and query explanation.9 npmMIT
- AlicenseBqualityCmaintenanceA lightweight Postgres MCP server for safe database exploration and query analysis, read-only by default, with multi-database support.412 PyPI4MIT
TDQS
Scored across 8 tools
The tools are mostly distinct: list_schemas, list_tables, describe_table, execute_query, and explain_query each target a different aspect of database exploration. The health, version, and ping_database tools have overlapping purposes around server status, but their descriptions clarify the differences, so only minor confusion is possible.
Most tool names follow a clear verb_noun pattern (list_schemas, ping_database, execute_query). However, 'health' and 'version' are bare nouns, deviating from the otherwise consistent style. The underscore convention is uniform throughout, keeping the naming readable.
With 8 tools, the server is well-scoped for a simple database MCP. Each tool covers a necessary function—server diagnostics, schema/table introspection, and query execution/planning—without unnecessary bloat or skimping.
For a read-only database tool, the surface is complete: users can discover schemas, explore tables and columns, run queries, and inspect query plans. Health and version cover server metadata. No obvious gaps exist for the intended read-only scope.