pg-inspect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection string (e.g., postgresql://user:pass@host:5432/dbname) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_schemasA | List non-system schemas in the connected database. |
| list_tablesA | List tables and views in a schema, with estimated row counts. |
| describe_tableA | Show columns, types, nullability and defaults for a table. |
| list_indexesB | List indexes on a table with their definitions. |
| table_statsB | Table size on disk, index size, and live/dead tuple estimates. |
| sample_rowsA | Fetch up to 50 sample rows from a table. |
| explain_queryA | Return the JSON query plan (EXPLAIN, no execution) for a SELECT/WITH query. |
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 7 tools
Each tool targets a distinct aspect of database inspection: schemas, tables, table structure, indexes, table statistics, sample data, and query plans. There is minimal overlap between them, and an agent can easily select the right tool based on the task.
The names mostly follow a consistent verb_noun pattern (list_schemas, list_tables, describe_table, list_indexes, sample_rows, explain_query). table_stats breaks the pattern slightly, being noun_noun rather than verb_noun, but it is still readable and predictable.
Seven tools is well-scoped for a PostgreSQL inspection server. Each tool serves a clear purpose without unnecessary redundancy, and the count fits comfortably within the ideal range.
The tool surface covers the primary inspection workflow: discovering schemas/tables, examining columns, viewing indexes, retrieving table statistics, sampling rows, and explaining queries. Minor gaps like constraint/foreign key information or listing database objects beyond tables exist, but they are not critical for basic inspection.