> Full Neon documentation index: https://neon.com/docs/llms.txt

# Neon Auth updates, Neon Auth MCP tools, and Stripe Projects guide

## Neon Auth: new plugins and settings

Neon continues to cover more of the backend stack, and auth is central to that. Four new Neon Auth features:

**Magic Link sign-in:** The Magic Link plugin lets users sign in via a link sent to their email, no password required. If you're using Neon Auth UI components, enable it with a single prop:

```tsx
<NeonAuthUIProvider
  authClient={authClient}
  magicLink
>
```

Enable the plugin from the Console or via the API. See [Magic Link plugin](https://neon.com/docs/auth/guides/plugins/magic-link).

**Phone number sign-in:** Existing users can sign in with an OTP delivered by SMS. You bring your own SMS provider, connected via a `send.otp` webhook. The sign-in flow is a two-step SDK call:

```ts
// Step 1: send the OTP
await authClient.phoneNumber.sendOtp({ phoneNumber });

// Step 2: verify the code and sign in
await authClient.phoneNumber.verify({ phoneNumber, code });
```

Enable the plugin from the Console or via the API. See [Phone number plugin](https://neon.com/docs/auth/guides/plugins/phone-number).

**Wildcard trusted domains:** Add a [wildcard trusted domain](https://neon.com/docs/auth/guides/configure-domains) like `https://*.my-app-preview.vercel.app` to cover all preview deployments under that pattern, instead of adding each hostname individually.

**Custom application name:** Set a custom name that appears in user-facing auth messages like verification emails. Configurable per branch, so development and production can use different names. See [Update auth configuration](https://neon.com/docs/auth/guides/manage-auth-api#update-auth-configuration).

**Tip:** Getting ready for production? The [Auth production checklist](https://neon.com/docs/auth/production-checklist) covers trusted domains, email provider setup, OAuth credentials, and more.

## Neon Auth MCP tools

Two new Neon Auth management tools are now available in the [Neon MCP server](https://neon.com/docs/ai/neon-mcp-server):

- **`configure_neon_auth`:** Configure your Neon Auth setup, including OAuth providers, email providers, and authentication methods.
- **`get_neon_auth_config`:** Retrieve your current Neon Auth configuration, including integration metadata.

If you haven't set up the Neon MCP server yet, run `npx neonctl@latest init`. Once connected, you can configure Neon Auth using natural language in your AI editor. For example:

```text
Set up Neon Auth for my project. Enable Google OAuth and email/password sign-in,
and set the application name to "My App".
```

See [Neon MCP server](https://neon.com/docs/ai/neon-mcp-server) for full setup details.

## Neon and Stripe Projects

Neon [works with Stripe Projects](https://neon.com/blog/neon-works-with-stripe-projects-for-agentic-provisioning), Stripe's platform for AI-native development. With the Stripe Projects CLI installed, your AI agent can provision a Neon Postgres database in a single command:

```bash
stripe projects add neon/postgres
```

Stripe Projects handles authentication and writes credentials directly to your `.env` file. No dashboards, no copy-pasting connection strings. See the [Neon with Stripe Projects guide](https://neon.com/guides/projects-dev-neon) for a complete example.

## Azure regions deprecation reminder

If your project uses an Azure region (`azure-eastus2`, `azure-westus3`, or `azure-gwc`), you have until **August 27, 2026** to migrate. See [Azure regions deprecation](https://neon.com/docs/import/azure-regions-deprecation) for timeline and migration options.