We just updated our VS Code extension - Deploy and manage databases, data, schemas, tables, branches, MCPs
Neon
    Docs
    Log inSign up
    /Changelog

    Changelog

    The latest product updates from Neon

    RSS feed

    New feature

    Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

    Another feature

    Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

    Third feature

    Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

    Fixes & improvements
    • Short bullet describing a fix or improvement.
    • Another short bullet, if applicable.

    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:

    Consumption API

    • We increased the burst limit for our Consumption API endpoints. The higher limit allows for temporary spikes in request volume, making it easier to handle periods of high activity without hitting rate limits.

      The Consumption API lets Neon Scale and Enterprise plan users track resource usage (compute time, storage, data transfer) across projects programmatically.

    Import Data Assistant

    • Fixed an issue where the Import Data Assistant would get stuck after creating a new project, preventing users from completing their database import.

      The Import Data Assistant, available from the Neon Console, helps you move an existing Postgres database to Neon using just a connection string.

    Neon VS Code Extension
    • Added support for configuring the Neon MCP Server in read-only mode. You can now restrict the MCP Server to read-only tools and read-only SQL transactions directly from the VS Code extension settings. See Neon VS Code Extension.

    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 Vercel variables

    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.

    New Neon logo

    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.

    Data anonymization
    • Data anonymization now supports custom masking rules defined via SQL or the Neon API. Custom masking rules appear as text in the data anonymization UI and are preserved when running anonymization, allowing you to safely mix Console, API, and SQL workflows.
    • Foreign key columns can no longer be masked directly to maintain referential consistency. Instead of showing masking rule suggestions, the data anonymization UI now displays an alert with an action to navigate to the corresponding primary key column. Clicking "Go to primary key" scrolls to and highlights the relevant primary key where you can set masking rules.
    Data API
    • Fixed an issue where project-scoped API keys could not read Data API status on organization-owned projects. The endpoint now uses project-level permissions instead of requiring organization-level access.
    Monitoring integrations
    • Error messages returned by Neon's monitoring integrations now display on integration cards on the Integrations page in your Neon project, making it easier to identify and troubleshoot integration issues.
    Neon Auth
    • Added a toggle in the Create Project dialog in the Neon Console that lets you enable Neon Auth when creating new projects.
    • OAuth provider credentials (client ID and client secret) are now hidden from organization members and collaborators. Only admin users can view these credentials in the Console.
    Neon MCP Server
    • Fixed read-only mode detection in OAuth flows for the Neon MCP Server. Read-only mode now properly restricts access based on OAuth scopes.
    • Added scope selection UI to the OAuth authorization flow, letting users optionally deselect write permissions when authorizing MCP clients.
    • Fixed account resolution when using project-scoped API keys. Previously, project-scoped API keys would cause errors when attempting to access account-level endpoints since these keys are restricted to project-level operations.
    • Fixed OAuth token verification regression that was causing authentication failures for users who authenticated via OAuth. The server now correctly checks OAuth tokens before falling back to API key verification.
    Was this page helpful?

    Subscribe to our changelog.
    No spam, guaranteed.