Connect PostgreSQL to Claude Code

Let Claude run scoped reads and writes against your PostgreSQL data. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect PostgreSQL to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect PostgreSQL, you add a PostgreSQL MCP server: a small hosted service that exposes PostgreSQL's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own PostgreSQL account. No API keys pasted into config files.

claude mcp add --transport http postgresql https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in PostgreSQL once connected?

Full read-write PostgreSQL access lets Claude query a table, insert or update rows, run a parameterized migration, and correct bad data once you approve. The database work that used to mean switching into psql or a SQL client happens where you are already describing the change in plain language.

Insert a new row into a specified table with given column values
Update or correct records that match a stated condition after approval
Run a parameterized query to fetch and summarize rows
Apply a schema migration such as adding a column or index
Delete rows matching a precise filter once you confirm
Inspect table schema, constraints, and indexes to plan a change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same PostgreSQL access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the PostgreSQL API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when PostgreSQL changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build PostgreSQL connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same PostgreSQL connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own PostgreSQL account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on PostgreSQL's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to PostgreSQL?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the PostgreSQL account it signs in with. Revoking access is one click in PostgreSQL.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.