Integration

Neon integration

Serverless Postgres database platform API. Manage projects, branches, databases, and compute endpoints. Create database branches for development, scale compute on demand. Essential for serverless apps, development workflows, and database management.

Connect Neon How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Neon.Built from the 33 Neon tools below, on the connection you add once.

Common Neon use cases

branch cleanup
user management
database provisioning
teardown
connection info
cost control
manual start
project view
user removal
branch rename

What you can do with Neon

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Branch, 7 operations

create_branchCreate branchPOSTCreates an instant copy-on-write branch from parent.
delete_branchDelete branchDELETEDeletes a branch and its associated endpoints.
get_branchGet branchGETRetrieves details for a specific branch.
list_branchesList branchesGETLists all branches in a project.
restore_branchRestore branchPOSTRestores a branch to a specific LSN or point in time.
set_default_branchSet default branchPOSTSets a branch as the default (primary) branch of a project.
update_branchUpdate branchPATCHUpdates a branch (e.g., rename).

Endpoint, 7 operations

create_endpointCreate endpointPOSTCreates a compute endpoint for a branch.
delete_endpointDelete endpointDELETEDeletes a compute endpoint.
get_endpointGet endpointGETRetrieves details for a specific compute endpoint.
list_endpointsList endpointsGETLists all compute endpoints in a project.
start_endpointStart endpointPOSTStarts a suspended compute endpoint.
suspend_endpointSuspend endpointPOSTSuspends a compute endpoint to stop billing.
update_endpointUpdate endpointPATCHUpdates compute endpoint settings such as autoscaling limits.

Database, 5 operations

create_databaseCreate databasePOSTCreates a new database in a branch.
delete_databaseDelete databaseDELETEDeletes a database from a branch.
get_databaseGet databaseGETRetrieves details for a specific database.
list_databasesList databasesGETLists all databases in a branch.
update_databaseUpdate databasePATCHUpdates a database in a branch.

Project, 5 operations

create_projectCreate projectPOSTCreates a new Neon project with Postgres database.
delete_projectDelete projectDELETEPermanently deletes a project and all its data.
get_projectGet projectGETRetrieves detailed information about a project.
list_projectsList projectsGETLists all Neon projects in the account.
update_projectUpdate projectPATCHUpdates settings for a Neon project.

Role, 5 operations

create_roleCreate rolePOSTCreates a new database role in a branch.
delete_roleDelete roleDELETEDeletes a database role from a branch.
get_roleGet roleGETRetrieves details for a specific database role.
list_rolesList rolesGETLists all database roles in a branch.
reset_role_passwordReset role passwordPOSTResets the password for a database role.

Operation, 2 operations

get_operationGet operationGETRetrieves details of a specific operation.
list_operationsList operationsGETLists all operations for a Neon project.

Connectionuri, 1 operation

get_connection_uriGet connection uriGETGenerates a connection string for a database.

Consumption, 1 operation

get_consumptionGet consumptionGETRetrieves consumption/usage metrics for a project.

Neon API rate limits

10 requests per second

Rate limits vary by plan

These are the limits Neon documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Neon documentation for current values.

Use Neon from Claude Code, Cursor or Codex

Connect Neon in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Neon operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Neon

Create your workspace
Sign up free. Nothing to install.
Connect Neon once
Add your Neon connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Neon integration FAQ

What can you do with the Neon integration?

LiveContext exposes 33 operations on Neon, covering branch, endpoint, database and project. Common uses include branch cleanup, user management and database provisioning.

What are the Neon API rate limits?

Neon documents 10 requests per second. Rate limits vary by plan Limits are set by Neon and can depend on your plan.