MCP Database Doctor vs Pgtuner MCP
A side-by-side look at the MCP Database Doctor and Pgtuner MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Database Doctor for databases work as a local process; choose Pgtuner MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Database Doctor when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
CONTROL_PLANE_URL. - You want tools like
analyze_query, check_migration, suggest_indexes.
Choose Pgtuner MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
DATABASE_URI. - You want tools like
get_slow_queries, analyze_query, get_table_stats.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 56/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | other |
| Pricing | Free | Free |
| Required env vars | CONTROL_PLANE_URL | DATABASE_URI |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 29 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 5 | 16 |
| Full listing | View MCP Database Doctor | View Pgtuner MCP |
Tools & capabilities
MCP Database Doctor tools 5
analyze_querySQL anti-patterns with severity and recommendationscheck_migrationDestructive DDL, index locking, constraints, rewrite and transaction riskssuggest_indexesConservative DDL candidates; not appliedexplain_planLarge sequential scans, row estimate errors, sort spills, high loopshealth_reportAggregate review of supplied artifacts only
Pgtuner MCP tools 16
get_slow_queriesRetrieve slow queries from pg_stat_statements with detailed stats (total time, mean time, calls, cache hit ratio). Excludes system catalog queries.analyze_queryAnalyze a query's execution plan with EXPLAIN ANALYZE, including automated issue detectionget_table_statsGet detailed table statistics including size, row counts, dead tuples, and access patternsanalyze_disk_io_patternsAnalyze disk I/O read/write patterns, identify hot tables, buffer cache efficiency, and I/O bottlenecks. Supports filtering by analysis type (all, buffer_pool, tables, indexes, temp_files, checkpoints).get_index_recommendationsAI-powered index recommendations based on query workload analysisexplain_with_indexesRun EXPLAIN with hypothetical indexes to test improvements without creating real indexesmanage_hypothetical_indexesCreate, list, drop, or reset HypoPG hypothetical indexes. Supports hide/unhide existing indexes.find_unused_indexesFind unused and duplicate indexes that can be safely droppedcheck_database_healthComprehensive health check with scoring (connections, cache, locks, replication, wraparound, disk, checkpoints)get_active_queriesMonitor active queries, find long-running transactions and blocked queries. By default excludes system processes.analyze_wait_eventsAnalyze wait events to identify I/O, lock, or CPU bottlenecks. Focuses on client backend processes.review_settingsReview PostgreSQL settings by category with optimization recommendations- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Database Doctor
{
"mcpServers": {
"mcp-database-doctor": {
"command": "npx",
"args": [
"-y",
"mcp-database-doctor"
],
"env": {
"CONTROL_PLANE_URL": "YOUR_CONTROL_PLANE_URL_HERE"
}
}
}
}
Pgtuner MCP
{
"mcpServers": {
"pgtuner-mcp": {
"command": "uvx",
"args": [
"pgtuner_mcp"
],
"env": {
"DATABASE_URI": "YOUR_DATABASE_URI_HERE"
}
}
}
}
Frequently asked questions
MCP Database Doctor is categorized under Databases and uses a local stdio subprocess. Pgtuner MCP belongs to Databases and uses a local stdio subprocess. Pick MCP Database Doctor for databases work and Pgtuner MCP for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Database Doctor is listed as free. Auth: no auth required. Pgtuner MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-database-doctor and pgtuner-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Database Doctor has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Pgtuner MCP has 53/100 (Good) with 4 views, 0 installs and 29 GitHub stars.