A side-by-side look at the Pgtuner MCP and Postgres Scout MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pgtuner MCP for databases work as a local process; choose Postgres Scout 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 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.
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 detection
get_table_statsGet detailed table statistics including size, row counts, dead tuples, and access patterns
analyze_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 analysis
explain_with_indexesRun EXPLAIN with hypothetical indexes to test improvements without creating real indexes
find_unused_indexesFind unused and duplicate indexes that can be safely dropped
check_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
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.
Pgtuner MCP is categorized under Databases and uses a local stdio subprocess. Postgres Scout MCP belongs to Databases and uses a local stdio subprocess. Pick Pgtuner MCP for databases work and Postgres Scout 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.
Pgtuner MCP is listed as free. Auth: other. Postgres Scout MCP has no declared pricing — check the project's own site. 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 pgtuner-mcp and postgres-scout-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pgtuner MCP has a quality signal of 52/100 (Good) with 3 views, 0 installs and 29 GitHub stars. Postgres Scout MCP has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.