Full-access PostgreSQL server for Model Context Protocol with read/write capabilities and enhanced schema metadata
Most database access work still happens through a UI a human drives. MCP Postgres Full Access MCP server moves it into the conversation instead. Full-access PostgreSQL server for Model Context Protocol with read/write capabilities and enhanced schema metadata.
A powerful Model Context Protocol server providing full read-write access to PostgreSQL databases. Unlike the read-only official MCP PostgreSQL server, this enhanced implementation allows Large Language Models (LLMs) to both query and modify database content with proper transaction management and safety controls.
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 8 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 structureConfiguration 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.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Postgres Full Access's toolset — execute_query, Input, execute_dml_ddl_dcl_tcl and 5 more — is a fair guide to whether it matches your workflow. It is maintained by syahiidkamil; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Postgres Full Access's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| 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 |
{
"mcpServers": {
"postgres-full": {
"command": "npx",
"args": [
"-y",
"mcp-postgres-full-access",
"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.