
Postgres Connector
io.github.martymarkenson/postgres-connector is a MCP server that lets AI agents query PostgreSQL databases over stdio.
About
Martymarkenson's postgres-connector is a minimal Model Context Protocol server that lets developers point Claude Code, Cursor, or similar clients at PostgreSQL so investigations happen in chat instead of a separate SQL client. During backend work you can validate assumptions about rows, test ad hoc SELECTs while writing handlers, or compare schema expectations against reality—provided you scope credentials to least-privilege and avoid exposing write access on production without review. The npm stdio transport (postgres-connector 1.0.2) keeps setup familiar for agent workflows already running other MCP tools. It is intermediate complexity: you must supply a connection string, network reachability, and judgment about what the agent is allowed to run. This is a database integration MCP, not a migration runner or hosted warehouse; pair it with your ORM and migration skills for schema changes.
- MCP bridge for PostgreSQL query execution from the agent
- stdio npm package postgres-connector v1.0.2
- Fits local dev, staging, or tunnelled production read replicas when you configure connection strings safely
- Lightweight connector focused on querying rather than full ORM management
Postgres Connector by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add postgres-connector -- npx -y postgres-connectorAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | postgres-connector |
|---|---|
| Transport | STDIO |
| Auth | None |
What it does
Connect your agent to a live PostgreSQL database so it can run read queries and inspect schema while you implement features or fix data bugs.
Who is it for?
Best when you have a Postgres-backed app and want the agent to explore data safely during backend development.
Skip if: Skip if you need governed BI semantics, row-level audit on every tool call, or databases other than PostgreSQL without another connector.
What you get
The agent can run authorized queries against your Postgres instance so answers reflect actual schema and sample rows in the same coding session.
- Query results and schema-aware answers grounded in live PostgreSQL data
- Faster iteration on SQL and API handlers without leaving the agent thread
By the numbers
- Package version 1.0.2 on npm identifier postgres-connector
- Transport: stdio
- Scope: querying PostgreSQL databases (per registry description)
Recommended MCP Servers
How it compares
Thin SQL query MCP for Postgres, not a full data pipeline, warehouse sync, or ORM code generator.
FAQ
Who is io.github.martymarkenson/postgres-connector for?
Developers and small teams building on PostgreSQL who want their coding agent to inspect and query the database during implementation and debugging.
When should I use io.github.martymarkenson/postgres-connector?
Use it in Build/backend work when you need to verify queries, understand relationships, or debug data issues while pairing with your agent on API or SQL changes.
How do I add io.github.martymarkenson/postgres-connector to my agent?
Install the npm stdio package postgres-connector v1.0.2, add it to your MCP server list, and configure your PostgreSQL connection string and network access per your agent's secrets handling.