Neon changed its API changelog

===================================================================
--- before
+++ after
@@ -15,8 +15,93 @@
 
 Email
 
 Subscribe
+Aug 28, 2026
+
+ADD NEON TO YOUR CODING AGENT
+
+Three new Neon CLI commands set up Neon in coding agents like Cursor and Claude Code, without manual config steps. Each runs an interactive walkthrough, or takes flags so you can script it.
+
+NEON MCP
+
+Installs the Neon MCP Server into your agents by writing their MCP config for you. It points each agent at the hosted server, sets up authentication, and can limit which tools the agent sees. By default, it mints a Neon API key and writes it into the config. Alternativevly, pass --oauth to skip API-key creation and have the agent sign in to Neon on first use instead.
+
+For example, install into Cursor and Claude Code with read-only tools:
+
+neon mcp --agent cursor --agent claude-code --read-only
+
+NEON SKILLS
+
+Installs Neon's agent skills so tools like Cursor and Claude Code know how to work with Neon's Postgres, AI Gateway, Object Storage, and Functions. Skills install into the current directory by default, so they travel with the repository, and neon skills update refreshes them to their latest versions later.
+
+For example, install the core Postgres and AI Gateway skills into Cursor:
+
+neon skills -s neon -s neon-ai-gateway --agent cursor
+
+NEON PLUGINS
+
+Installs the neon-postgres plugin into agents that support plugin marketplaces, such as Claude Code, Cursor, and Codex. The plugin bundles Neon's agent skills and MCP access in one package, so a single install gives the agent both.
+
+For example, install into Claude Code without prompts:
+
+neon plugins --agent claude-code -y
+
+The Neon CLI has seen many new additions over the past several weeks. For a tour of other recent additions, from the branch-first workflow to built-in Postgres diagnostics, see Just landed in the Neon CLI.
+
+HAVE AN IDEA FOR THE CLI OR AGENT TOOLS?
+
+We'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.
+
+POSTGRES MINOR VERSION ROLLOUT HISTORY NOW IN THE DOCS
+
+Our Postgres version support policy docs now include a rollout history for recent minor releases. For each release, you can see the date PostgreSQL published it, the versions it included, when it became available on Neon, and how long that took. For example:
+
+Postgres release dateVersions in the releaseFirst available on NeonTime to availability2026-08-1318.6, 17.11, 16.15, 15.19, 14.242026-08-185 days
+
+Each version in the table links to its PostgreSQL release notes, so you can see exactly which bug fixes and CVE patches that minor release contains.
+
+INFO
+
+Run SELECT version(); to see which version you're on. Minor version updates are rolled out the next time your compute restarts. To update now, restart your compute yourself, or wait for your compute's next scheduled update. See Updates for details.
+
+GET STARTED BUILDING ON THE NEON BACKEND
+
+Two new guides show what you can build with the Neon backend, where Object Storage, Functions, and the AI Gateway sit next to your database:
+
+ * Build an image processing API with Neon Functions, Sharp, and Neon AI Gateway: resize, crop, optimize, analyze, and AI-caption images on Neon Functions, then store the results in your branch's Object Storage bucket.
+ * Clean up orphaned S3 objects with Neon Object Storage branching: run a real storage-cleanup job on a branch first, where buckets branch with your database, then promote it to production once you've verified it.
+
+[/_next/image?url=%2F_next%2Fstatic%2Fimmutable%2Fmedia%2Fpattern.0f2sshrf3n3qc.png&w=384&q=75]
+Try the Neon backend, free during the beta
+
+Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and branch with your Postgres database, so your whole stack forks together.
+
+Get started
+
+CONNECT FX TO NEON'S MCP SERVER
+
+fx is a small, fast coding agent and CLI from Vercel Labs, built to embed in larger systems. You can now connect it to Neon's remote MCP server, using either OAuth or a Neon API key, so the agent can work with your Neon projects directly.
+
+For example, add the server with OAuth:
+
+npx add-mcp https://mcp.neon.tech/mcp -a fx
+
+Then authorize from the fx shell:
+
+/mcp auth neon --open
+
+For the API key option and more detail, see Connect MCP clients to Neon.
+
+FIXES & IMPROVEMENTS
+
+Neon MCP server updates
+ * The inspect_database tool now includes a stalled-queries check. It returns a compute-wide snapshot of every client backend and parallel worker whose query group has been running longer than 30 seconds, so an agent can see what's blocking a database right now, across every database on the compute and from the moment a query stalls.
+ * Stalled queries are now ranked with the oldest query group first, so the longest-running blocker surfaces at the top of the results.
+
+New NAT gateway IPs and Private Networking endpoints in us-east-2
+ * Added NAT gateway IP addresses and Private Networking VPC endpoint service names in AWS US East (Ohio) (us-east-2). If you allowlist Neon's outbound IPs, add the new addresses from the Regions page, or outbound connections can fail intermittently. If you use Private Networking in this region, add the new service names from the Private Networking guide.
+
 Aug 21, 2026
 
 FASTER LAKEBASE SEARCH SETUP
 
@@ -58,9 +143,9 @@
 The Neon MCP server is now listed in Claude's connectors. You can manage Neon from Claude: create projects and branches, run SQL, change schemas, and diagnose a slow query.
 
 In Claude.ai or Claude Desktop, go to Settings > Connectors, click Browse connectors, add Neon, and authorize access to your Neon account.
 
-Neon connector in Claude [/docs/changelog/claude_neon_connector.png?dpl=dpl_8RL9SPonhEaLkGezJjoDvdqrx8ku]
+Neon connector in Claude [/docs/changelog/claude_neon_connector.png?dpl=dpl_BbQruGcKMCzJrXu4NRznc6LzVc5w]
 
 INSTALL NEON AGENT SKILLS WITH PI
 
 You can now install Neon Agent Skills with Pi, straight from the repository:
@@ -162,104 +247,8 @@
 If you allowlist Neon's NAT gateway IPs on external systems, add the new addresses, or connections may be affected intermittently.
 
 See Regions for the full IP list and the Private Networking guide for VPC endpoint services by region.
 
-Aug 07, 2026
-
-A NEW CONSOLE LAYOUT FOR THE NEON BACKEND
-
-The Console sidebar has a new shape. Every branch-level Neon backend service now sits at the same level.
-
- * Postgres database is everything that was in the sidebar before: Tables, SQL Editor, Backup & Restore, Computes, Data API, Roles, and Databases, now under one collapsible item.
- * Auth, Object storage, Functions, and AI Gateway backend services sit alongside it as siblings.
-
-Above that section, the sidebar separates what belongs to project (Dashboard, Branches, Integrations, Settings) from what belongs to the branch (Overview, Credentials, Monitoring, Child branches). The branch picker sits between them, so it's clear which branch you're looking at when you open a service.
-
-Overview is now a summary of the branch you have selected. It lists each backend service with its status, so you can see what the branch actually has enabled without opening each one:
-
-The new Neon Console sidebar alongside the branch Overview page, which lists Postgres database, BetterAuth, Object storage, Functions, and AI Gateway with their status [/docs/changelog/backend_nav.png?dpl=dpl_8RL9SPonhEaLkGezJjoDvdqrx8ku]
-
-Each service shows whether it's enabled on the branch, so the page doubles as a list of what you can still add.
-
-MORE REGIONS FOR BACKEND SERVICES COMING SOON
-
-Object Storage, Functions, and the AI Gateway services are available only in AWS US East (Ohio) (aws-us-east-2). More regions are coming soon.
-
-MORE MODELS ON THE AI GATEWAY
-
-We've expanded the models available through the Neon AI Gateway, including Kimi K3, GLM-5.2, Inkling, and new additions to the Gemini and GPT families.
-
-The catalog now spans frontier and open-weight models from OpenAI, Anthropic, Google, Meta, Moonshot AI, Alibaba, Zhipu AI, and Thinking Machines. One credential and one base URL reach all of them, so trying a different model means changing a string rather than signing up with another provider:
-
-curl -X POST "$NEON_AI_GATEWAY_BASE_URL/v1/chat/completions" \
-  -H "Authorization: Bearer $NEON_AI_GATEWAY_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"model": "kimi-k3", "messages": [{"role": "user", "content": "What is Neon?"}]}'
-
-Browse the full catalog in the model reference, where you can filter by provider or open weights and open any model for a copy-paste quickstart. To see what your own project can reach right now, call GET /v1/models.
-
-SET UP THE NEON BACKEND WITH YOUR AI AGENT
-
-To build with the beta services including AI Gateway, install the Neon agent skills so your assistant knows how to provision and wire them up:
-
-npx neon@latest init
-
-Then ask your assistant to get started with Neon. See the backend beta guide for access and setup, or How a Neon backend fits together for a tour of all five capabilities.
-
-PROJECT-LEVEL PERMISSIONS FOR ALL ORGS
-
-Last week we introduced project-level permissions to newly created organizations. Existing organizations are now supported, so every team on Neon has the four organization roles (Admin, Editor, Viewer, and Collaborator) and per-project permissions.
-
-See Neon now has per-project permissions for the announcement, and User permissions for the complete documentation.
-
-GET STARTED WITH PROJECT PERMISSIONS
-
-Go from everyone-sees-everything to scoped access in about five minutes. Read the guide.
-
-API KEYS AND MULTIPLE ACCOUNTS IN THE NEON CLI
-
-There are two new additions to the Neon CLI that go together: api-keys mints credentials, and profile stores them and switches between them. Together they let you give an agent a credential that reaches exactly one project, or work across a personal account and a work organization without juggling config directories.
-
-NEW TO THE NEON CLI?
-
-Install it with npm install -g neon, then authenticate with neon auth. See the install guide and CLI quickstart to get going.
-
-MANAGE API KEYS WITH NEON API-KEYS
-
-Minting a key used to mean opening the Console or hand-rolling a neon api request. neon api-keys now covers listing, creating, and revoking keys at every scope:
-
-neon api-keys create --name ci                                        # account key
-neon api-keys create --name ci --org-id org-example-12345678          # organization key
-neon api-keys create --name agent --project-id green-breeze-12345678  # one project only
-
-Project-scoped keys are the reason this matters. A key created with --project-id can't create projects, can't mint more keys, and can't see any other project, which makes it safe to hand to an agent or a CI job instead of sharing your account.
-
-See the neon api-keys reference and Manage API keys for key types and permissions.
-
-USE MORE THAN ONE ACCOUNT WITH NEON PROFILE
-
-The CLI could only hold one account at a time, so anyone working across two built their own workaround out of --config-dir and shell aliases. A profile is a name pointing at a credentials file, selected per invocation with --profile or NEON_PROFILE:
-
-neon auth --profile work                                            # create or re-authenticate
-neon deploy --profile work                                          # use it
-neon profile create ci --mint --project-id green-breeze-12345678    # or hold a scoped key, no browser
-
-A profile can hold a browser sign-in or an API key, which is where it meets the scoped keys above. --mint signs in once, keeps only the minted key, and signs the session back out, so afterwards nothing about the profile can open a browser.
-
-The CLI also now stores its configuration in $XDG_CONFIG_HOME/neon, or ~/.config/neon if that isn't set. A pre-existing neonctl directory is still read in place, so there's no migration step.
-
-See the neon profile reference for the full command set and for how --profile resolves against NEON_API_KEY.
-
-NEW NAT GATEWAY IPS AND VPC ENDPOINT SERVICES IN EUROPE (FRANKFURT)
-
-We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region (eu-central-1) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.
-
-UPDATE YOUR IP ALLOWLISTS
-
-If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new NAT gateway addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.
-
-If you use Private Networking in eu-central-1, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.
-
 Was this page helpful?
 YesNo
 Thank you for your feedback!
 Edit on GitHub