vibe-provision
Configures Clerk authentication, setting up redirect URLs and injecting environment variables for authentication.
Registers a domain with Resend for email sending and provides related environment variables.
Creates Stripe products, prices, and webhook endpoints for payment processing.
Creates a Supabase project and retrieves API keys for database and authentication.
Generates a terraform.tfvars.json file with provisioned resource values for use with Terraform.
Provisions an Upstash Redis database and provides connection credentials.
Automatically injects environment variables into Vercel projects.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vibe-provisionProvision Clerk auth and Stripe payments for my SaaS app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vibe-provision
Provision external SaaS services from YAML. One command to set up Clerk, Stripe, Resend and inject .env.
"AI can write code, but it can't click dashboards." — vibe-provision solves that.
Quick Start
# 1. Generate a config template
npx vibe-provision init
# 2. Authenticate with providers (one-time)
npx vibe-provision auth
# 3. Provision resources and generate .env
npx vibe-provision upThat's it. Your .env is ready — run your dev server.
vp is a short alias: npx vp up works too.
Related MCP server: Daemoon
vibe.yaml
project: my-saas-app
output:
- .env
- vercel # auto-inject env vars to Vercel
- terraform # generate terraform.tfvars.json
services:
auth:
provider: clerk
config:
app_name: "My SaaS App"
redirect_urls:
- http://localhost:3000/callback
payments:
provider: stripe
config:
products:
- name: "Pro Plan"
prices:
- amount: 1900
currency: usd
interval: month
webhooks:
events:
- checkout.session.completed
- customer.subscription.updated
email:
provider: resend
config:
domain: my-app.com
database:
provider: neon
config:
region: aws-ap-northeast-1
cache:
provider: upstash
config:
region: ap-northeast-1AI (Cursor, Claude Code, etc.) can generate this file alongside your app code.
Supported Providers
Provider | Category | What it creates | Auth method |
Clerk | Auth | Redirect URL config + env vars | API key paste |
Stripe | Payments | Products, Prices, Webhook Endpoints | API key paste |
Resend | Domain registration | API key paste | |
Supabase | DB + Auth | Project + API keys | Access token |
Neon | Postgres | Project + database | API key |
Upstash | Redis | Database | Email + API key |
Output Targets
Control where env vars are written via the output section:
Target | Description |
| Local |
| Vercel environment variables via CLI |
|
|
Environment-Specific Config
Use --env to manage multiple environments:
npx vp up --env dev # merges vibe.yaml + vibe.dev.yaml → .env.dev
npx vp up --env staging # merges vibe.yaml + vibe.staging.yaml → .env.staging
npx vp up --env prod # merges vibe.yaml + vibe.prod.yaml → .env.prod
npx vp up # uses vibe.yaml only → .envBase config (vibe.yaml) holds shared settings. Override files (vibe.{env}.yaml) deep-merge on top:
# vibe.dev.yaml — only override what differs
services:
payments:
provider: stripe
config:
webhooks:
url: https://dev.example.com/api/webhooks/stripeMCP Server (AI Agent Integration)
vibe-provision includes an MCP server so AI agents (Claude Code, Cursor) can provision services directly.
Setup
Add to your .mcp.json (global or per-project):
{
"mcpServers": {
"vibe-provision": {
"command": "npx",
"args": ["vibe-provision", "mcp"]
}
}
}Available Tools
Tool | Description |
| Check auth and provisioning state for all providers |
| Provision resources and generate .env (requires prior auth) |
| Add a new service to vibe.yaml |
Example Flow
User: "Add Stripe payments to my app"
→ AI generates vibe.yaml with stripe config
→ AI calls vibe_provision_status → "stripe: NOT authenticated"
→ AI: "Run npx vp auth in your terminal"
→ User authenticates (one-time)
→ AI calls vibe_provision_up → Products, Prices, Webhooks created
→ .env updated, app ready to runIdempotency
vibe-provision up is safe to run multiple times. It tracks created resources in .vibe-provision/state.json and skips anything that already exists.
How It Works
init— generates avibe.yamltemplateauth— walks you through authenticating each provider, stores credentials locally in~/.vibe-provision/auth/up— readsvibe.yaml, calls provider APIs to create resources, writes to configured output targets
Credentials never leave your machine.
Examples
saas-starter-simple — Next.js + Clerk + Stripe + Resend, direct webhook handling
saas-starter — Same stack + qhook for production webhook processing
Development
npm install
npm run lint # type check
npm test # run tests (47 tests)
npm run dev -- init # run CLI in dev modeLicense
FSL-1.1-Apache-2.0 — Free to use for any purpose except competing hosted services. Converts to Apache 2.0 on 2028-03-26.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables AI agents to discover, evaluate, and provision cloud infrastructure across AWS, GCP, and Azure with cross-cloud normalization, cost comparisons, and deployable execution kits.Last updated52MIT- Alicense-qualityBmaintenanceGives AI coding agents (Claude Code, Cursor, etc.) unified, secure access to dev infrastructure (Vercel, GitHub, Supabase, Cloudflare, GCP) via a single MCP token.Last updatedMIT

Daemoonofficial
Alicense-qualityBmaintenanceEnables AI coding agents to access and manage multiple dev infrastructure providers (Vercel, GitHub, Supabase, Cloudflare, GCP) through a single MCP token and unified API.Last updatedMIT- Alicense-qualityDmaintenanceEnables AI agents to autonomously provision, pay for, and manage S3-compatible storage and vector databases without human intervention.Last updatedMIT
Related MCP Connectors
SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.
The agent-native cloud: database, functions, AI, storage, auth and more. 50 tools, one API key.
One PAT, any MCP agent: Vercel, GitHub, Cloudflare, Supabase, GCP — unified dev infra gateway.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/totte-dev/vibe-provision'
If you have feedback or need assistance with the MCP directory API, please join our Discord server