Neon
Your Postgres, within reach of the agent
Ask — and act on — your Neon Postgres in plain language
Official Neon server: manage projects, branches, and run SQL.
Neon is serverless Postgres — databases with branching, so you can spin up a copy of your data the way you branch code. The official connector, published by Neon, is "an open-source tool that lets you interact with your Neon Postgres databases in natural language." It acts as a bridge between what you ask and the Neon API, translating your requests into the calls needed to create projects and branches, run queries, and perform database migrations.
Ask "give me a summary of all my Neon projects and what data is in each one" and it reads your account and answers. Say "create a database called my-database with a users table" and it sets it up — no SQL, no clicking through the console. It talks to Neon with your API key, so it can do anything you can do from your own account.
What you can ask
- "Let's create a new Postgres database, and call it 'my-database'. Then create a table called users with the columns: id, name, email, and password."
- "I want to run a migration on my project 'my-project' that alters the users table to add a new column called 'created_at'."
- "Can you give me a summary of all of my Neon projects and what data is in each one?"
What token you need
You need a Neon API key — the key that lets software act on your Neon account.
- Sign in at console.neon.tech and open your account settings.
- Follow the Neon API Keys guide to generate a new key, then copy it.
- Paste it when the Lab asks for
NEON_API_KEY. It's stored encrypted in your Keychain.
The API key can create, change, and delete real projects and data, so treat it like a password. A word of caution, straight from Neon: this local server is intended for local development and IDE integrations only — Neon does not recommend using it in production, because it can execute powerful operations that may lead to accidental or unauthorized changes. Always review and authorize what the agent proposes before it runs.
We open the app and set it up in Claude Code (and your other Macs).
How it works with Terminal Sync
Set up the connector once on one machine. Terminal Sync keeps your claude_desktop_config.json encrypted in your Drive, so on any other machine where you open Claude Code, the connector is already there.