mcp-database-doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTROL_PLANE_URL | No | URL for the control plane, used only by the hosted HTTP process (set in .env before running `npm run start:hosted`). Not needed for the free, offline local stdio MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_queryB | Offline PostgreSQL SQL heuristics. No execution; no finding is not proof of safety. |
| check_migrationA | Review PostgreSQL migration SQL for destructive operations, lock/rewrite risks and transaction conflicts. Does not execute. |
| suggest_indexesA | Conservative index candidates for single unquoted table queries. Requires EXPLAIN validation; never applies DDL. |
| explain_planA | Interpret a supplied PostgreSQL EXPLAIN FORMAT JSON plan. Does not run EXPLAIN ANALYZE. |
| health_reportA | Aggregate diagnostics over supplied artifacts, not live database health. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.