Integration · Databases
AI agents for Neon
Manage Neon serverless Postgres through the Neon API.
- Actions
- 7
- Read
- 5
- Write
- 2
Actions
What your agents can do in Neon
Manage Neon serverless Postgres through the Neon API: list projects, branches and databases, read a database's schema (its tables, columns and keys as SQL), compare two branches' schemas, and create or delete branches, with a Neon API key. It does not run SQL queries.
Read 5
Look things up. Nothing changes.
List projects
Lists the Neon projects the key can reach, as projects: each with its id (the project ID other actions take), name, region_id, pg_version, created_at and storage use.
List branches
Lists a project's branches, newest change first, as branches: each with its id (br-…), name, parent_id, whether it is the default branch, whether it is protected, current_state and created_at.
List databases
Lists the Postgres databases on a branch, as databases: each with its name (the name other actions take), owner_name (the role that owns it) and created_at.
Get a database's schema
Reads a database's schema on a branch as SQL DDL in sql: every table with its columns, types, defaults, keys and indexes, and the views, functions and other objects (no data).
Compare two branches' schemas
Shows how a database's schema on one branch differs from another branch (its parent when base_branch_id is left out), as a unified diff of the SQL DDL in diff.
Write 2
Create, change or send.
Create a branch
Creates a copy-on-write branch of a project's data, instantly and without copying.
Delete a branchDeletes data
Deletes a branch with its databases and computes, breaking any open connections to it.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Neon account.
What you enter
- API key
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Neon data
Ask a question in plain words. The agent can list projects, list branches or list databases in Neon, then answers with what it found.
- 02
Let an agent update Neon
Have the agent create a branch or delete a branch in Neon as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Neon and Slack: it can list projects in Neon and post a summary to a Slack channel in the same run.
FAQ
Neon and MyDeepAgents
Can MyDeepAgents connect to Neon?
Yes. The Neon connector has 7 actions: 5 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Neon?
Paste an API key from your Neon account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Neon without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Neon in workflows as well as agents?
Yes. Every Neon action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Neon to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.