Provider · Database

Neon — Ashlr Stack Provider

Neon: Serverless Postgres. Creates a project and pools the connection string. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Database · PAT

Neon — Serverless Postgres. Creates a project and pools the connection string.

Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.

stack add neon

Or retrieve catalog matches for what you're building via stack recommend:

stack recommend "serverless postgres for a B2B SaaS"

Auth flow

Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.

How-to: Paste a personal API key from https://console.neon.tech/app/settings/api-keys.

Secret slots

stack add neon has these 2 catalog secret slots; verify which values its adapter actually materializes through Phantom:

NEON_API_KEY
DATABASE_URL

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

MCP wiring

Neon has an MCP entry in the catalog. An adapter may write a descriptor to .mcp.json. Inspect the actual file and complete supported client and credential setup; Claude Code / Cursor / Windsurf availability is not established by the descriptor. Shell expressions in JSON remain literal.

@neondatabase/mcp-server-neon with NEON_API_KEY piped from Phantom — branch, migrate, and query from the agent.

Starter templates that include Neon

Selected template init attempts provider setup by default; add --noProvision to inspect config first:

stack init --template nextjs-neon-vercel-sentry

Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.
Turso — Edge SQLite (libSQL). Creates a database in your default org.
Convex — Reactive backend-as-a-service. Deploy key stored in Phantom.
Upstash — Serverless Redis + Kafka. Management token stored in Phantom.
Firebase — Realtime DB + Auth. Service-account JSON stored verbatim in Phantom.

FAQ

Do I need a Neon account to use it with Stack?

Use an existing Neon account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://console.neon.tech and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Neon credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (NEON_API_KEY, DATABASE_URL); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove neon` for local Neon configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Neon credentials through https://console.neon.tech, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.