Neon MCP integration for AI agents.
Connect AI agents to Neon through 18 structured actions, including get branch, create branch, and delete branch. Review authentication, inputs, workflows, an…
- ACTION CONTRACTS
- 18
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Neon integration exposes
The Neon Agent App exposes 18 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent get detailed metadata for a neon branch, create a branch in a neon project, and delete a branch from a neon project. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Neon account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Neon capabilities.
Showing 12 of 18 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_branchREADGet detailed metadata for a Neon branch.
INPUTS: projectId / branchId
create_branchWRITECreate a branch in a Neon project.
INPUTS: projectId / name / parentId / parentLsn / parentTimestamp
delete_branchHIGH IMPACTDelete a branch from a Neon project.
INPUTS: projectId / branchId
create_databaseWRITECreate a database in a Neon branch.
INPUTS: projectId / branchId / name / ownerName
create_projectWRITECreate a Neon project with an optional default branch configuration.
INPUTS: name / orgId / regionId / pgVersion / branchName
delete_databaseHIGH IMPACTDelete a database from a Neon branch.
INPUTS: projectId / branchId / databaseName
delete_projectHIGH IMPACTDelete a Neon project.
INPUTS: projectId
get_current_userREADGet the currently authenticated Neon user profile.
get_databaseREADGet detailed metadata for a Neon database.
INPUTS: projectId / branchId / databaseName
get_operationREADGet detailed metadata for a Neon operation.
INPUTS: projectId / operationId
get_projectREADGet detailed metadata for a Neon project.
INPUTS: projectId
list_branchesREADList branches for a Neon project.
INPUTS: projectId / search / sortBy / sortOrder / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
get_branch
projectIdREQUIRED- The Neon project ID.
branchIdREQUIRED- The Neon branch ID.
create_branch
projectIdREQUIRED- The Neon project ID.
nameREQUIRED- The Neon branch name.
parentIdOPTIONAL- Parent branch ID used as the source for the new branch.
parentLsnOPTIONAL- Log Sequence Number on the parent branch used to create the new branch.
parentTimestampOPTIONAL- Point-in-time timestamp on the parent branch used to create the new branch.
delete_branch
projectIdREQUIRED- The Neon project ID.
branchIdREQUIRED- The Neon branch ID.
create_database
projectIdREQUIRED- The Neon project ID.
branchIdREQUIRED- The Neon branch ID.
nameREQUIRED- Name of the database to create.
ownerNameREQUIRED- Role name that should own the new database.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Branch
Get detailed metadata for a Neon branch. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_branchControl Create Branch
Create a branch in a Neon project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_branchVerify with Get Current User
Get the currently authenticated Neon user profile. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Neon with explicit limits
- Authorize Neon with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_branch`, `delete_database`, and `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Neon rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Neon task completed successfully.
CONNECTION MODEL
API key
Neon API key used with the Authorization Bearer header. Create it in Account settings > API keys in the Neon Console: https://neon.com/docs/manage/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Neon.