mcp-database-doctor
Related Servers
Alternatives to mcp-database-doctor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables agents to review PostgreSQL EXPLAIN plans and compare before-and-after plans, ranking likely performance problems and suggested fixes without connecting to a database.360 npmMIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform deterministic database architecture audits and performance engineering for PostgreSQL and MySQL, covering migration analysis with schema health scoring, ESR-based composite index recommendations, N+1 query detection, EXPLAIN plan diagnosis, transaction and deadlock analysis, partitioning and archival design, and capacity or configuration tuning. It also generates phased Expand & Contract runbooks that turn blocking DDL into zero-downtime production migrations.8MIT
- AlicenseAqualityAmaintenanceReviews MySQL migrations, queries and application code before they run, flagging table locks, full table copies, data loss, missing indexes, integer overflow and SQL injection, with a safe rewrite for each finding. Runs locally; your SQL never leaves your machine.6Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceAnalyzes SQL queries for performance issues, provides optimization suggestions with automated rewriting, and recommends indexes across multiple database dialects (PostgreSQL, MySQL, Oracle, SQL Server).1MIT
- AlicenseNot gradedqualityBmaintenanceEnables static, database-free SQL health checks that return rule-based findings and verdicts, propose executable fixes, and verify rewrites are equivalent while comparing execution plans and suggesting indexes. Supports batch/file/git-diff review for CI gating, all at zero-dependency Tier0.MIT
- AlicenseNot gradedqualityAmaintenanceEnables checking Postgres migration SQL against a table-size estate snapshot and safety policy before apply, returning approve/block verdicts with lock details and remediation guidance, plus tools to explain locks and list policy rules.1MIT
TDQS
Scored across 5 tools
Each tool targets a distinct artifact: raw SQL (analyze_query), migration SQL (check_migration), index candidates (suggest_indexes), EXPLAIN JSON plans (explain_plan), and aggregated artifacts (health_report). analyze_query and suggest_indexes both operate on queries, so there is mild overlap, but their differing outputs keep them separable.
Four of five names follow a clean verb_noun pattern (analyze_query, check_migration, suggest_indexes, explain_plan). health_report breaks the pattern as a noun_noun label, a minor deviation that is still readable.
Five tools is well-scoped for an offline PostgreSQL diagnostic suite, with each tool covering a distinct analysis dimension and no redundant entries.
The surface covers the core diagnostic dimensions for a read-only, offline advisory role: query heuristics, migration risk, index advice, plan interpretation, and health aggregation. No write/live-DB operations are expected given its stated non-executing purpose, though a dedicated schema/config check is absent.