Postgres
Connect PostgreSQL—the default for many indie SaaS stacks—to your coding agent through MCP for schema checks and SQL during feature work.
Overview
io.github.marcelo-ochoa/postgres is a MCP server for the Build phase that lets coding agents interact with PostgreSQL over stdio using a connection string and POSTGRES_USER/POSTGRES_PASSWORD.
What is this MCP server?
- @marcelo-ochoa/server-postgres v1.0.8 with stdio MCP transport
- PostgreSQL connection string argument plus POSTGRES_USER and POSTGRES_PASSWORD env vars
- Enables agent-driven interaction with PostgreSQL from MCP clients
- Source in marcelo-ochoa/servers repository subfolder src/postgres
- Fits alongside Supabase, Neon, or self-hosted Postgres dev instances
- Published version 1.0.8 as @marcelo-ochoa/server-postgres on npm
- Stdio transport with positional connectionString for PostgreSQL
- POSTGRES_USER and POSTGRES_PASSWORD environment variables in server schema
What problem does it solve?
Without a Postgres MCP bridge, indie builders repeatedly export schema dumps or paste query results so the agent can help with backend code.
Who is it for?
SaaS and API builders on Postgres, Neon, or Supabase who already use MCP in Claude Code or Cursor for day-to-day coding.
Skip if: Pure frontend prototypes with no database, or teams that forbid any agent-connected credentials regardless of environment.
What do I get? / Deliverables
Once registered, the agent can work against your Postgres instance through MCP, keeping data exploration aligned with the files you are editing.
- Live Postgres MCP integration for your coding agent
- In-session SQL and schema assistance against your PostgreSQL database
- Stdio MCP setup documented at package version 1.0.8
Recommended MCP Servers
Journey fit
Postgres is most often touched while building and integrating the product data layer, which is why this MCP server shelves under Build. Integrations captures protocol-level hooks to external data stores that agents call from the IDE, which is exactly what this server provides.
How it compares
MCP Postgres connector for agents, not a Prisma skill or database migration generator.
Common Questions / FAQ
Who is io.github.marcelo-ochoa/postgres for?
It is for solo builders and small teams on PostgreSQL who want their MCP coding agent to inspect schema and run SQL on dev or staging databases.
When should I use io.github.marcelo-ochoa/postgres?
Use it while building backend features, debugging queries, or validating integrations when Postgres is your system of record.
How do I add io.github.marcelo-ochoa/postgres to my agent?
Add @marcelo-ochoa/server-postgres to your MCP servers list with stdio transport, the PostgreSQL connection string, and POSTGRES_USER/POSTGRES_PASSWORD as required.