Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Neon in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI manage Neon serverless Postgres: projects, branches, compute endpoints, databases, roles, schemas, operations and consumption. It can create branches and start or suspend computes after your confirmation. Never returns passwords. With a Neon API key.
Try asking
Example prompts for Neon
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Neon, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Neon
Let your AI manage Neon serverless Postgres: projects, branches, compute endpoints, databases, roles, schemas, operations and consumption. It can create branches and start or suspend computes after your confirmation. Never returns passwords. With a Neon API key.
Setup
- In the Neon Console, open Account settings → API keys for a personal key (it acts as you, in every organization you belong to), or Organization settings → API keys for a key that reaches only that organization's projects. A project-scoped key reaches a single project.
- Create the key and copy it at once: Neon shows it only once. Paste it into
NEON_API_KEYand install the connector. The key is sent only to console.neon.tech. - Check the setup with
neon_list_organizations: it lists the organizations the key belongs to, with theirorg_id.
What it covers: organizations, projects, branches, compute endpoints, databases, roles, database schemas, operations and consumption, through the Neon API v2. The AI walks down from neon_list_projects to neon_get_project, neon_list_branches, neon_list_endpoints, neon_list_databases, neon_list_roles and neon_get_database_schema, which shows the tables, columns, indexes and constraints of a database, also as they were at a past time. With a personal key, organization projects need the org_id.
Asks before every change: neon_create_branch, neon_start_endpoint and neon_suspend_endpoint change your project, so the AI tells you what will happen and waits for your yes.
- A running compute uses compute hours, which count against your plan's allowance or are billed on paid plans.
neon_start_endpointstarts that meter; computes scale to zero by themselves after the suspend timeout. neon_suspend_endpointcloses every open connection to that compute at once.neon_create_branchmakes an instant copy-on-write branch, optionally from a point in time. Branches beyond your plan's allowance can be billed, and a compute added to the branch starts right away. Give temporary branches an expiry date.- Every change runs as an operation in the background;
neon_list_operationsandneon_get_operationshow when it has finished.
Switched off at install: neon_delete_branch, which deletes a branch together with its computes. An administrator turns it on deliberately. The root and default branch can never be deleted.
Usage and cost: neon_get_consumption returns compute time, storage, branch counts and network transfer per project, by hour, day or month. It needs the org_id, works on paid plans only (Launch, Scale, Business, Enterprise) and does not wake any compute. Project and branch details also show this period's compute time, active time, written data and data transfer.
No passwords, no SQL: role passwords and connection strings are never returned, so no database password reaches the AI. This connector does not run SQL either: Neon's SQL over HTTP needs a connection string with the role's password, not the API key. To query your data, add the PostgreSQL connector with a dedicated read-only Postgres role on your Neon host (port 5432, SSL required). neon_get_database_schema still shows the structure without any password.
Common errors: 401: the API key is wrong or was revoked; create a new one. 403: the key may not reach that project or organization (a project or organization key used elsewhere), or your plan does not include the feature, for example consumption history. 404: wrong project, branch or endpoint id. 423 Locked: another operation is running on the project; wait for it and retry. 429: too many requests; wait a moment and retry.
The connector does not create or delete projects, databases or roles, reset passwords, or cover Neon Auth, the Data API, snapshots or organization administration.
Prerequisites: NEON_API_KEY
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick Neon and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
neon_list_organizations | List the Neon organizations the API key belongs to, with org_id, name, handle and plan |
neon_list_projects | List Neon projects with id, name, region, Postgres version, organization, storage size and last compute activity |
neon_get_project | Get one Neon project: region, Postgres version, default compute settings, history retention, and this billing period's compute time, active… |
neon_list_branches | List the branches of a Neon project with id, name, parent, state, default and protected flags, logical size and this period's compute time |
neon_get_branch | Get one Neon branch: name, parent and branch point, state, default and protected flags, expiry, logical size and this period's compute and… |
neon_create_branch | Create a Neon branch (an instant copy-on-write copy of a parent branch, optionally at a point in time) |
neon_delete_branch | Delete a Neon branch and its computes, ending all their connections |
neon_list_endpoints | List the compute endpoints of a Neon project: id, branch, read-write or read-only, state (active, idle), autoscaling range in compute… |
neon_get_endpoint | Get one Neon compute endpoint: state, branch, type, autoscaling range, suspend timeout, last activity, start and suspend times and host name |
neon_start_endpoint | Start (wake) a Neon compute endpoint |
neon_suspend_endpoint | Suspend a Neon compute endpoint now, which stops compute billing but closes every open connection to it |
neon_list_databases | List the Postgres databases of a Neon branch with name and owner role |
neon_list_roles | List the Postgres roles of a Neon branch with name, protected flag and authentication method |
neon_get_database_schema | Get the schema of one database on a Neon branch (tables, columns, types, indexes, constraints, as pg_dump-style SQL), optionally as it was… |
neon_list_operations | List the operations of a Neon project (branch creation, compute start and suspend, config changes), newest first, with status, error and… |
neon_get_operation | Get one Neon operation: action, status (scheduling, running, finished, failed, cancelled), error, retries and duration |
neon_get_consumption | Get Neon consumption per project and period: compute unit seconds, root and child branch storage, instant restore storage, extra branches… |
Example prompts
- "List all our Neon projects with region, Postgres version and storage size, and tell me which ones had no compute activity this month."
- "Show me the schema of the app database on our production branch: tables, columns and indexes."
- "Create a branch called feature-billing from main that expires in 7 days. Tell me what it may cost before you create it."
- "Which computes are active right now? Suspend the one on the preview branch, but ask me first."
- "How much compute time and storage did each project use last month?"
Next steps
Was this guide helpful?
