What an agent can do in Neon
Work with Neon serverless Postgres: list and create projects and branches, run SQL, inspect schemas and tables, and prepare migrations on a branch.
Jobs on Rush that use Neon
- How Much Neon Did Each Client Use Last Month? A Software Agency's Usage Report for Invoices
- What Were Our Numbers Last Month? An Investor-Update App's Read-Only Metrics From Each Startup's Neon Database
How Neon connects
Neon is a remote MCP server, published by Neon, at https://mcp.neon.tech/mcp. Connecting it signs in through the MCP OAuth flow on Neon's side.
From Neon: Neon's MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names neon in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Neon",
"url": "https://mcp.neon.tech/mcp"
}Whose Neon account the agent uses
Your Neon connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Neon, and a run started with an API key uses the Neon of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Neon, and that agent's runs use their account and nothing else: never yours, never another user's.
More Database integrations
Frequently asked questions
How do I connect Neon to Rush?
Open Settings → Connections in the console and connect Neon, or send POST /me/connections with {"type":"mcp","name":"Neon","url":"https://mcp.neon.tech/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Neon account?
No. A run gets your Neon connection only when it names it in connections ("connections": ["neon"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Neon?
Work with Neon serverless Postgres: list and create projects and branches, run SQL, inspect schemas and tables, and prepare migrations on a branch. 2 published jobs use it; this page lists them.
Can my app's users connect their own Neon?
Yes. Make each user an agent from your template, and they sign in to their own Neon through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to