Databases & storage
Neon
Connect a Neon organization with a Viewer member's API key, plus optional just-in-time write elevation.
Neon connects with up to two API keys: a read key Dave uses on its own, and an
optional elevation key Dave uses only for writes you approve. Dave reads with the
official neon CLI and looks up Neon’s documentation through Neon’s docs MCP server.
Neon has no read-only key type — every key can do whatever its owner can. So what Dave can do on its own depends on whose key you paste, not on which field you paste it into. Pick a setup under Permissions before you connect.
Connect
Section titled “Connect”-
In the Neon Console, open your organization’s Settings and copy the Organization ID — it starts with
org-. -
Create the read key — and, if you want Dave to make changes, the elevation key — for the setup you chose under Permissions. Neon shows each key once.
-
In Dave, go to Integrations → Add integration → Neon.
-
Paste the Organization ID and the read key into API key. Keys are stored encrypted and never shown again.
-
Set a Label — see labels.
-
Optionally paste the elevation key into Elevation API key — see Just-in-time elevation.
-
Choose Connect Neon. Dave checks the keys with Neon; you do not need to stay on the page.
Permissions
Section titled “Permissions”Choose a setup
Section titled “Choose a setup”| Setup | API key (read) | Elevation API key | What Dave can do |
|---|---|---|---|
| Recommended | Personal key of a Viewer member | Organization key, project-scoped key, or personal key of an Editor or Admin | Reads on its own. Every change waits for your approval. |
| Read-only | Personal key of a Viewer member | — | Reads only. It can never change anything. |
| Your own key | Your personal key, as an Editor or Admin | Not possible | Anything your account can do, without asking you. |
Read key: add a Viewer member
Section titled “Read key: add a Viewer member”Organization members are free on every Neon plan, so a dedicated member costs
nothing — it only needs an email address you control, such as
dave-readonly@yourcompany.com.
-
In the Neon Console, open your organization’s People page and choose Invite member.
-
Enter the address and give it the Viewer role.
-
Accept the invite, sign in as that member, and create a personal key under Account settings → API keys.
A Viewer can see projects, branches, computes, databases, roles and operations, but cannot run SQL or see connection strings, so Dave never touches your data with it. Dave checks the key by listing the organization’s projects.
Elevation key
Section titled “Elevation key”Optional. A second key that can write. Any of these work, as long as it is not from the same account as the read key:
- Organization API key — not tied to any user, so it is the simplest choice when you are the only Admin. Only Admins can create one, under Organization → Settings → API keys.
- Project-scoped key — limits writes to one project. Created in the same place.
- Personal key of an Editor or Admin — for example your own.
Dave rejects an elevation key from the same account as the read key, because it would grant nothing more.
Manage the connection
Section titled “Manage the connection”Personal keys are listed under Account settings → API keys; organization and project-scoped keys under Organization → Settings → API keys. Revoking the read key cuts Dave off; revoking the elevation key disables elevation.
Disconnect in Dave stops Dave using both keys immediately, but does not revoke them in Neon. The same goes for cancelling an unfinished setup.
To replace either key, or to add or remove elevation, disconnect and connect again.
Just-in-time elevation
Section titled “Just-in-time elevation”Dave stores the elevation key encrypted and the agent never sees it: each write you approve — creating a branch, resizing a compute, changing a project setting — is sent through Dave as a one-shot, 15-minute grant for exactly the API calls shown. Elevation covers the Neon API only; it never runs SQL. Leave the field blank to keep the organization read-only.
Troubleshooting
Section titled “Troubleshooting”- Neon rejects the credentials — check the organization ID and that the key is active and its member belongs to that organization, then connect again.
- Neon rejects the elevation key — check it is active and was not pasted into the wrong field.
- The elevation key belongs to the same account as the read key — use an organization API key, or a key from a different member. See Elevation key.