Changelog

Neon backend in Europe, plus new AI Gateway models

The Neon backend is now available in AWS Europe (Frankfurt) (aws-eu-central-1), alongside AWS US East (Ohio) (aws-us-east-2). If you build in Europe, you can now run these services closer to your users and data.

The AI Gateway catalog also gains new models, callable through the same API and key as the rest of the catalog:

• Fable 5.1
• GLM 5.3 Flash
• Grok 4.6
• OpenAI GPT-6 Astra (landing soon)

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and AWS Europe (Frankfurt), and branch with your Postgres database, so your whole stack forks together.

Get started

Neon is now available in Grok Bot

Neon is now available as a plugin in Grok Bot. Connect your Neon account once, then ask a Grok bot to work with your database:

• Create a project and get a connection string for your app
• Spin up an isolated branch before testing a migration
• List projects and spot databases you no longer need
• Run SQL against your database
• Set up routines that summarize database usage

The plugin pairs Neon agent skills with the Neon MCP server, so Grok Bot has both the context and the authenticated tools to act on your account.

To install, open the Neon plugin in Grok Bot and authorize Neon in the browser. You can also open Grok Bot's Plugins directory and search for Neon, or ask Grok to connect the Neon plugin. Read more in the blog post.

Neon CLI updates

Two updates to the Neon CLI for setting up and connecting your projects:

• A leaner neon init: it now does one focused job based on where you run it: in an empty directory it scaffolds a template and installs agent tooling (like neon bootstrap); in an existing app it installs a plugin (or skills and MCP), links your project, and writes a neon.ts config. Run it with npx, and pass -y and --agent for unattended runs:

  npx neon@latest init

• neon env pull writes Neon Function invocation URLs: each function's public URL is written as NEON_FUNCTION_<SLUG>_BASE_URL, so one function can reach another from the environment. See Environment variables.

  neon env pull

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.

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:

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.

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.

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

Faster Lakebase Search setup

Lakebase Search is now easier to install. You can install both Lakebase Search extensions (lakebase_vector and lakebase_text) directly with the following CREATE EXTENSION statements from your SQL client or the Neon SQL Editor:

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Previously, you had to run an SQL statement first to load the supporting libraries.

We also updated both extensions to newer versions (lakebase_vector 1.0.1 and lakebase_text 0.1.1). If you already have them installed, see Update an extension to get the latest version.

Postgres minor version updates

We updated supported Postgres versions to 14.24, 15.19, 16.15, 17.11, and 18.6. Minor releases bring you the latest upstream Postgres fixes and security patches.

When a new minor version is available, Neon applies it the next time your compute restarts. For more about how we handle PostgreSQL minor version updates, refer to our Postgres version support policy.

Neon CLI updates

Store credentials in your OS keyring. You can now keep a profile's credential in your operating system's keyring instead of a file. Pass --keyring to neon auth or neon profile create:

neon auth --keyring

The secret is stored in the macOS Keychain, Windows Credential Manager, or Linux Secret Service.

Inspect every database at once. neon inspect db now inspects every database on the branch when you omit the database name, adding a database column to the output. Pass the database name to inspect a single database, which also scopes locks and long-running-queries so their names resolve correctly.

Neon MCP server now an official Claude connector

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.

Install Neon Agent Skills with Pi

You can now install Neon Agent Skills with Pi, straight from the repository:

pi install git:github.com/neondatabase/agent-skills

Pi reads the skills directly, so there's no separate sync step. This joins the existing install channels, including npx skills, the Cursor, Claude Code, Codex, and Kimi Code plugins, and neon init.

New Neon Functions guides

Two new guides show what you can build on Neon Functions, which run alongside your database as part of the Neon backend:

• Automate Neon Functions deployments with GitHub Actions: set up CI/CD to deploy to production on merge and create preview functions for pull requests.
• Monitor Neon Functions with Sentry: add error tracking, structured logs, and request tracing.

Try the Neon backend

Object Storage, Functions, and AI Gateway branch with your Postgres database, so your whole stack forks together.

Get started