A fully featured PostgreSQL server adapter for the Model Context Protocol (MCP), providing robust read/write access and enhanced schema metadata for
A fully featured PostgreSQL server adapter for the Model Context Protocol (MCP), providing robust read/write access and enhanced schema metadata for LLM and AI-powered applications. Supports full SQL DML/DDL operations. That is what the postgresql full access mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This project is an independently maintained and extended fork of the original mcp-postgres-full-access by Syahiid Kamil.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 9 tools. What each one is for:
execute_query — Execute read-only SQL queries (SELECT statements)Input — sql (string): The SQL query to executeexecute_dml_ddl_dcl_tcl — Execute data modification operations (INSERT, UPDATE, DELETE) or schema changes (CREATE, ALTER, DROP)execute_maintenance — Execute maintenance commands like VACUUM, ANALYZE, or CREATE DATABASE outside of transactionsexecute_commit — Explicitly commit a transaction by its IDexecute_rollback — Explicitly rollback a transaction by its IDlist_tables — Get a comprehensive list of all tables in the databasedescribe_table — Get detailed information about a specific table structurelist_schemas — Get a list of all schemas in the databaseConfiguration is passed through the environment: TRANSACTION_TIMEOUT_MS, MAX_CONCURRENT_TRANSACTIONS, PG_STATEMENT_TIMEOUT_MS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. PostgreSQL Full Access's toolset — execute_query, Input, execute_dml_ddl_dcl_tcl and 6 more — is a fair guide to whether it matches your workflow. It is maintained by kamusis; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| execute_query | Execute read-only SQL queries (SELECT statements) |
| Input | sql (string): The SQL query to execute |
| execute_dml_ddl_dcl_tcl | Execute data modification operations (INSERT, UPDATE, DELETE) or schema changes (CREATE, ALTER, DROP) |
| execute_maintenance | Execute maintenance commands like VACUUM, ANALYZE, or CREATE DATABASE outside of transactions |
| execute_commit | Explicitly commit a transaction by its ID |
| execute_rollback | Explicitly rollback a transaction by its ID |
| list_tables | Get a comprehensive list of all tables in the database |
| describe_table | Get detailed information about a specific table structure |
| list_schemas | Get a list of all schemas in the database |
{
"mcpServers": {
"postgres-full": {
"command": "npx",
"args": [
"-y",
"mcp-postgres-full-access-extended",
"postgresql://username:password@localhost:5432/database"
],
"env": {
"TRANSACTION_TIMEOUT_MS": "60000",
"MAX_CONCURRENT_TRANSACTIONS": "5",
"PG_STATEMENT_TIMEOUT_MS": "30000"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TRANSACTION_TIMEOUT_MS | Configuration value read at startup. | Optional |
| MAX_CONCURRENT_TRANSACTIONS | Configuration value read at startup. | Optional |
| PG_STATEMENT_TIMEOUT_MS | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.