---
title: Neon Auth on Vercel previews, neon init enhancements, and more
---
## Neon Auth on Vercel previews
Both the [Vercel-managed](/docs/guides/vercel-managed-integration) and [Neon-managed](/docs/guides/neon-managed-vercel-integration) 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](/docs/auth/overview).
To see this in action, check out this new end-to-end guide: [Testing Auth Changes Safely with Vercel and Neon Branching](/guides/vercel-neon-auth-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:
```bash
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](/changelog/2025-12-19#easier-setup-for-neon-mcp-server) and VS Code Extension [in January](/changelog/2026-01-09#introducing-the-new-neon-vs-code-extension)), 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](/docs/ai/connect-mcp-clients-to-neon) and [Get started with the Neon VS Code Extension](/docs/local/vscode-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](https://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](https://neon.com/blog/new-neon-logo).
**Data anonymization**
- [Data anonymization](/docs/workflows/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](/docs/data-api/overview) 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](/docs/guides/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](/docs/auth/overview) 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](/docs/ai/ai-intro). 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.