Connect Neon Postgres

Agents create and compare Neon branches, describe tables and run SQL on serverless Postgres; you sign in to Neon and choose read-only or read-write access.

Once Neon Postgres is connected, an agent can list and create projects and branches, describe tables and columns, run SQL, apply schema changes on a branch and compare it with main, and manage computes and snapshots.

Before you start

A Neon account with access to the organisation and projects you want to use.
Decide how much access the agents should have. Neon's authorisation screen lets you choose a read-only scope. With full access, an agent can create and delete branches and run any SQL, so Neon recommends it for development and testing rather than production.
If a project uses IP Allow, add Neon's MCP addresses 34.192.103.46 and 23.22.233.166 to the allowlist, or connections will be refused.
You must be an owner or admin of the woble workspace.

Nothing to copy: Neon uses a sign-in flow.

Connect it

Open Marketplace, go to the Integrations tab, find Neon Postgres and press Connect.
Press Continue with Neon Postgres. A new tab opens at neon.tech. Sign in if you are not already.
On the authorisation page, review the permissions and choose read-only if you only want the agents to inspect and query. If you belong to more than one organisation, pick the right one when asked. Press Authorize.
The tab closes. The card shows Connected and the agent panel lists the new Neon tools.

Or ask an agent

Type @ruby connect Neon Postgres in any chat. The same card appears in the conversation. Only owners and admins can complete it.

Try it

"@atlas list the branches in the billing project and describe the subscriptions table on main."
"@ruby create a branch from main called try-index, add an index on events(account_id, created_at) there and tell me how the query plan changes."

If it does not connect

Connection refused with an IP error: the project has IP Allow enabled and Neon's MCP addresses are not on the list.
Read-only chosen but writes needed: press Remove in Marketplace, Connected, and connect again choosing full access.
Wrong organisation or expired authorisation: press Test connection; if it fails, Remove and reconnect, picking the right organisation.

Disconnect

Open Marketplace, Connected, and press Remove on Neon Postgres. The tokens are deleted and agents lose the Neon tools immediately.