Provider · Deploy

Vercel — Ashlr Stack Provider

Vercel: Frontend platform. Stores a scoped access token for deploys + env sync. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Deploy · PAT

Vercel — Frontend platform. Stores a scoped access token for deploys + env sync.

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 vercel

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

stack recommend "host a Next.js frontend"

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 access token from https://vercel.com/account/tokens.

Secret slots

stack add vercel has these 1 catalog secret slot; verify which values its adapter actually materializes through Phantom:

VERCEL_TOKEN

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

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

Vercel MCP server with VERCEL_TOKEN piped from Phantom — list deployments, tail logs, sync env.

Starter templates that include Vercel

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

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

Modal — Serverless compute for AI + data. Token stored in Phantom.
Railway — Infra from a repo. Project-level token stored in Phantom.
Fly.io — VMs at the edge. Machines API token stored in Phantom.
Cloudflare — Workers, R2, D1. Account id inferred from the token's scope.
Render — Zero-config hosting. API key stored in Phantom.

FAQ

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

Use an existing Vercel 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://vercel.com/dashboard and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Vercel credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (VERCEL_TOKEN); 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 vercel` for local Vercel configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Vercel credentials through https://vercel.com/dashboard, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.