Postgres
Read-only PostgreSQL MCP server. Drop-in replacement for the archived server-postgres.
The Postgres MCP server that stays read-only. A drop-in replacement for the archived
@modelcontextprotocol/server-postgres.
Switch in one line
Where your AI client starts the archived server today:
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
}
}
}
change the package name:
"args": ["-y", "@kaiva/postgres-mcp", "postgresql://localhost/mydb"]
In Claude Code:
claude mcp add postgres -- npx -y @kaiva/postgres-mcp postgresql://localhost/mydb
The query tool, its sql input and the table schema resources are the same, so nothing else
changes.
Other ways in, with DATABASE_URL set in your environment:
- Claude Code plugin:
/plugin install postgres-mcp --marketplace ai-kaiva/postgres-mcp - Gemini CLI extension:
gemini extensions install https://github.com/ai-kaiva/postgres-mcp, thengemini extensions config kaiva-postgres-mcpto enter the database URL - Docker:
docker run -i --rm -e DATABASE_URL ghcr.io/ai-kaiva/postgres-mcponce the image is published
Why switch
The archived server is no longer maintained: Anthropic archived it in 2025 as a reference example
rather than production software, and npm marks it "Package no longer supported". It runs whatever
text it is given inside BEGIN TRANSACTION READ ONLY, and that is not enough:
COMMIT; DROP SCHEMA public CASCADEends the read-only transaction and drops the schema (reported by Datadog Security Labs in August 2025; the fix never reached npm, where 0.6.2 is still the latest version).- With a superuser login, which is what most local and Docker installs start with, one statement
can run a shell command on the database server: PostgreSQL runs
COPY ... TO PROGRAMinside a read-only transaction.
We checked both against version 0.6.2 on PostgreSQL 14: both ran. Kaiva Postgres MCP refuses both.
| Archived 0.6.2 | Kaiva Postgres MCP | |
|---|---|---|
A second statement after COMMIT |
Runs | Refused: one statement per call, and PostgreSQL itself refuses a second |
COPY ... TO PROGRAM, server file reads, dblink |
Run, if the login allows | Refused |
| Time limit | None | 15 seconds per statement, 3 seconds waiting for a lock |
| Rows returned | All of them | The first 1,000, and it says so |
| Superuser login | Used as given | Warning on this machine; refused for a database on another machine unless you allow it |
| Tables listed | public schema only |
Every schema |
| Dates and timestamps | Turned into JavaScript dates, which can shift a date to the day before | Exactly as PostgreSQL prints them |
| Errors | Returned as protocol errors | Returned to the AI with what to fix |
| Maintained | No | Yes |
Tools
query: run one read-only SQL statement (SELECT,WITH,VALUES,TABLE,SHOWorEXPLAIN) and get the rows as JSON.list_tables: the tables and views this login can read, with type, estimated row count and comment.describe_table: one table's columns, primary key, unique and foreign keys, the tables that reference it, and its indexes.
Resources: each table's columns, as the archived server listed them.
How read-only is enforced
On every call:
- The SQL is checked before it is sent: one statement, starting with
SELECT,WITH,VALUES,TABLE,SHOWorEXPLAIN, calling no function that reaches past the transaction (dblink, server file functions,lo_importandlo_export,pg_terminate_backend, advisory locks, and functions that run SQL given to them as text). - It runs alone, through PostgreSQL's extended query protocol, which refuses a second statement,
inside a
READ ONLYtransaction with a statement time limit and a lock time limit. - The transaction is always rolled back, and
DISCARD ALLresets the session, so nothing a statement sets up outlives it.
From the project's README.