About postgres
An MCP server for read-only PostgreSQL inspection and query analysis. It helps database users review schemas and execution plans, check table statistics, and generate AWR-style performance reports.
Key features
- 01Read-only SQL queries
- 02SQL execution plans
- 03Table statistics
- 04PostgreSQL AWR-style reports
- 05Per-table schema resources
Use cases
- 01Inspect a PostgreSQL schema
- 02Analyze read-only SQL queries
- 03Review query execution plans
- 04Find database performance issues
MCP support
Exposes read-only PostgreSQL queries, execution plans, table statistics, AWR-style reports, and schema resources to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @marcelo-ochoa/server-postgresPOSTGRES_USERPostgreSQL userPOSTGRES_PASSWORDSecretPostgreSQL passwordLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| sql | string | Yes | The SQL query to execute |
| model | string | Yes | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| mcp_client | string | Yes | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
Details
From the project READMEPostgreSQL
A Model Context Protocol server that provides read-only access to PostgreSQL databases. This server enables LLMs to inspect database schemas and execute read-only queries.
Components
Tools
-
pg-query
- Execute read-only SQL queries against the connected database
- Input:
sql(string): The SQL query to execute - All queries are executed within a READ ONLY transaction
-
pg-stats
- Get statistics for a specific table
- Input:
name(string): The name of the table to get statistics for
-
pg-explain
- Explain Plan for a given SQL query
- Input:
sql(string): The SQL query to explain
-
pg-connect
- Connect to a PostgreSQL database
- Inputs:
connectionString(string): The PostgreSQL connection string without credentials (e.g. postgresql://host:port/dbname or host:port/dbname)user(string): The PostgreSQL usernamepassword(string): The PostgreSQL password
Example: pg-connect host.docker.internal:5432/postgres postgres pg_2025
- pg-awr
- Generate a PostgreSQL performance report similar to Oracle AWR. Includes database statistics, top queries (requires pg_stat_statements extension), table/index statistics, connection info, and optimization recommendations.
Resources
The server provides schema information for each table in the database:
- Table Schemas (
postgres://<dbname>/<table>/schema)- JSON schema information for each table
- Includes column names and data types
- Automatically discovered from database metadata
Change Log
See Change Log for the history of changes.
Configuration
The PostgreSQL server uses environment variables or the pg-connect tool for secure credential management:
PG_USER: PostgreSQL username (optional if usingpg-connect)PG_PASSWORD: PostgreSQL password (optional if usingpg-connect)
Connection String
The connection string should contain only the host, port, and database information (without embedded credentials). Providing it as a command-line argument is optional. If omitted at startup, you must use the pg-connect tool to establish a connection before using other functionality.
Supported connection string formats:
postgresql://host:port/dbnamehost:port/dbname
To enable encryption (SSL), append ?sslmode=require to the connection string or set the PG_SSL environment variable to true.
Usage with Claude Desktop
To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:
Docker
- When running Docker on macOS, use
host.docker.internalif the PostgreSQL server is running on the host network (e.g., localhost) - Credentials are passed via environment variables
PG_USERandPG_PASSWORD
{
"mcpServers": {
"postgres": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "PG_USER=myuser",
"-e", "PG_PASSWORD=mypassword",
"mochoa/mcp-postgres"
]
}
}
}
Note: You can still provide the connection string as a final argument if you want to connect automatically on startup: "args": [..., "mochoa/mcp-postgres", "postgresql://host.docker.internal:5432/mydb"].
NPX
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-postgres",
"postgresql://localhost:5432/mydb"
],
"env": {
"PG_USER": "myuser",
"PG_PASSWORD": "mypassword"
}
}
}
}
Replace /mydb with your database name.
Note: Replace the following placeholders with your actual values:
myuserandmypasswordwith your PostgreSQL credentialslocalhost:5432with your PostgreSQL server host and portmydbwith your database name
Usage with VS Code
For quick installation, use one of the one-click install buttons below...
For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.
Note that the
mcpkey is not needed in the.vscode/mcp.jsonfile.
Docker
Note: When using Docker and connecting to a PostgreSQL server on your host machine, use host.docker.internal instead of localhost in the connection URL.
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "pg_user",
"description": "PostgreSQL username"
},
{
"type": "promptString",
"id": "pg_password",
"description": "PostgreSQL password",
"password": true
}
],
"servers": {
"postgres": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "PG_USER=${input:pg_user}",
"-e", "PG_PASSWORD=${input:pg_password}",
"mochoa/mcp-postgres",
"postgresql://localhost:5432/mydb"
]
}
}
}
}
Note: You can add an input for pg_url and append it to args if you want to connect on startup.
NPX
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "pg_user",
"description": "PostgreSQL username"
},
{
"type": "promptString",
"id": "pg_password",
"description": "PostgreSQL password",
"password": true
}
],
"servers": {
"postgres": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-postgres",
"postgresql://localhost:5432/mydb"
],
"env": {
"PG_USER": "${input:pg_user}",
"PG_PASSWORD": "${input:pg_password}"
}
}
}
}
}
PostgreSQL AWR in action
See PostgreSQL AWR in action for an example of a performance report generated by the pg-awr tool for a production Moodle database, highlighting critical performance issues and optimization opportunities.
Demos
See Demos for usage examples with Claude Desktop, Docker AI, Gemini CLI, and Antigravity Code Editor.
Building
Docker:
docker build -t mochoa/mcp-postgres -f src/postgres/Dockerfile .
Sources
As usual the code of this extension is at GitHub, feel free to suggest changes and make contributions, note that I am a beginner developer of React and TypeScript so contributions to make this UI better are welcome.
📜 License
This project is licensed under the Apache License, Version 2.0 for new contributions, with existing code under MIT - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.