Changelog

Give your AI assistant Neon expertise

Install our Agent Skills to teach your AI coding assistant about Neon best practices, connection methods, ORM setup, and branching workflows. Works across Claude Code, Cursor, VS Code, and other AI tools.

npx skills add neondatabase/agent-skills

Agent Skills work alongside the Neon MCP Server. The skill provides reasoning and guidance while the MCP server provides capabilities like creating branches and running queries. Learn more in our blog post on Agent Skills.

MCP Server provisions Data API

The Neon MCP Server now supports provisioning the Neon Data API for your databases with optional JWT authentication. Ask your AI assistant:

Can you provision Data API access for my database with Neon Auth authentication?

The provision_neon_data_api tool enables HTTP-based access to your Neon databases and supports multiple authentication options: unauthenticated access, Neon Auth, or external providers (Clerk, Auth0, Stytch, and others). This makes it easier to set up Data API access directly from your AI assistant without switching to the Neon Console.

To get started with the Neon MCP Server, run npx neonctl@latest init to install and configure it automatically. Learn more in Neon MCP Server.

Postgres protocol 3.2 support

Neon now supports Postgres 18's protocol 3.2 with enhanced cancellation keys. This protocol support applies retroactively to all Postgres versions (14, 15, 16, 17, and 18). Clients that support the new protocol will automatically benefit from these improvements without any configuration changes needed.

Get started with Neon faster

We've added quick actions to the Neon docs. Everything you need to go from docs to working code is now just a click away.

Quick actions available on every doc page:

• Copy page as markdown
• Open in ChatGPT or Claude
• Copy neon init command for MCP Server setup
• Connect MCP on Cursor or VS Code

Find the prompts on the documentation homepage or try them here:

• 

  Next.js
• 

  Django
• 

  Drizzle
• 

  React Router
• 

  TanStack Start
• 

  Express
• 

  NestJS
• 

  Astro
• 

  SvelteKit
• 

  Nuxt

Neon Auth on Vercel previews

Both the Vercel-managed and Neon-managed integrations now automatically provision Neon Auth on preview branches when enabled on your production branch. Preview deployments get the NEON_AUTH_BASE_URL and VITE_NEON_AUTH_URL environment variables configured automatically.

Neon Auth provides managed authentication that stores user profiles in your database. When your database branches, auth data branches with it, making it easy to test authentication in isolated preview environments. Learn more.

To see this in action, check out this new end-to-end guide: Testing Auth Changes Safely with Vercel and Neon Branching.

One command for Neon MCP Server and VS Code Extension

The neon init command now configures both the Neon MCP Server and the Neon VS Code Extension in a single step:

npx neonctl@latest init

This command authenticates via OAuth, creates a Neon API key, and sets up:

• Neon MCP Server — Lets AI assistants manage your Neon projects, branches, and databases through natural language commands
• Neon VS Code Extension — Brings database schema browsing, SQL editing, and table data management directly into your IDE

Previously introduced as separate features (MCP Server setup in December and VS Code Extension in January), you can now get your complete AI-powered database development environment configured with one command in Cursor or VS Code.

For more information, see Connect MCP clients to Neon and Get started with the Neon VS Code Extension.

New Neon logo

You might notice a new Neon logo across the site, dashboard, and docs. Same Neon. New mark.

The logo is refreshed while staying true to the elephant and N we founded the company with. This update brings Neon's visual identity into the Databricks universe as we continue growing together, helping more than a million developers ship faster with Postgres.

If you reference Neon in your product, docs, or integrations, download the official assets at neon.com/brand. The page includes logo files, usage guidelines, and brand-safe variants for light and dark backgrounds.

For more on the design thinking behind the new logo, see the blog post.

New graphs for monitoring pooled connections

Neon uses PgBouncer for connection pooling, allowing thousands of client connections to share a smaller pool of actual Postgres connections. The monitoring page in the Neon Console now includes Pooler client connections and Pooler server connections graphs (these display data when you use a pooled connection). The Pooler client connections graph shows connections from your applications to PgBouncer, while Pooler server connections displays the actual connections from PgBouncer to Postgres. These graphs help you understand connection usage patterns, identify bottlenecks, and determine when to adjust your pool size or compute resources. For more information, see Monitoring dashboard.

Additionally, the OpenTelemetry and Datadog integrations now export PgBouncer connection pooling metrics, giving you visibility into pooler client and server connections in your observability platform alongside the new charts in the Neon Console. New integrations automatically include these metrics. To enable them for existing integrations, you can either edit the integration settings to trigger a collector upgrade or delete and recreate the integration.

GitHub Action support for Neon Auth and Data API

The Neon Create Branch GitHub Action now supports retrieving branch-specific URLs for Neon Auth and the Neon Data API. This makes it easy to run integration tests against isolated branch environments with the same auth and data access patterns you use in production. Set get_auth_url: true or get_data_api_url: true in your workflow to access the auth_url and data_api_url outputs for your test branch.

- name: Create Neon Branch
  uses: neondatabase/create-branch-action@v6
  id: create-branch
  with:
    project_id: ${{ vars.NEON_PROJECT_ID }}
    branch_name: feature-branch
    api_key: ${{ secrets.NEON_API_KEY }}
    get_auth_url: true
    get_data_api_url: true
- name: Use outputs
  run: |
    echo "Auth URL: ${{ steps.create-branch.outputs.auth_url }}"
    echo "Data API URL: ${{ steps.create-branch.outputs.data_api_url }}"

Introducing the new Neon VS Code Extension

The Neon VS Code Extension brings a revamped database development experience directly into your IDE. Connect to your Neon organizations, projects, and branches, browse schemas in a rich tree view, run SQL queries, and view or edit table data in a spreadsheet-like interface—all without leaving your editor.

This release replaces the previous Neon Local extension. The new extension no longer uses a local proxy or localhost connection strings. Instead, it helps you manage direct Neon connection strings for your branches.

The extension also automatically configures the Neon MCP Server, enabling AI-powered workflows for managing projects, branches, and databases from your coding agent.

Available for VS Code, Cursor, Windsurf, and other VS Code-compatible editors. Get started with the Neon VS Code Extension.