Vibe Provision

Name: Vibe Provision
Author: totte-dev

by totte-devversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.totte-dev/vibe-provision

Install

Overview

Description from the maker (original English)

Provision SaaS services from YAML and inject .env. Supports Clerk, Stripe, Resend and more.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vibe-provision": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-provision"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vibe-provision -- npx -y vibe-provision

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibe-provision": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-provision"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vibe-provision": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vibe-provision"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account totte-dev, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

More stars than 0% of the other 1748 servers in this category
Published to the registry more recently than 3% of the other 1748 servers in this category
Basic checks equal to or better than 100% of the other 1748 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vibe Provision safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce: open-source B2B and marketplace ecommerce

by spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

Runs in the cloud★ 15,812BSD-3-ClauseUpdated 7 days ago

Install

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago

Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 27 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 up

That's it. Your .env is ready — run your dev server.

vp is a short alias: npx vp up works too.

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-1

AI (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	Email	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
`.env`	Local `.env` file (default)
`vercel`	Vercel environment variables via CLI
`terraform`	`.vibe-provision/terraform.tfvars.json` with merge semantics

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 → .env

Base 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/stripe

MCP 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
`vibe_provision_status`	Check auth and provisioning state for all providers
`vibe_provision_up`	Provision resources and generate .env (requires prior auth)
`vibe_provision_add`	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 run

Idempotency

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 a vibe.yaml template
`auth` — walks you through authenticating each provider, stores credentials locally in ~/.vibe-provision/auth/
`up` — reads vibe.yaml, calls provider APIs to create resources, writes to configured output targets

Credentials never leave your machine.

Examples

[saas-starter-simple](./examples/saas-starter-simple/) — Next.js + Clerk + Stripe + Resend, direct webhook handling
[saas-starter](./examples/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 mode

License

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.

Vibe Provision

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

vibe-provision

Quick Start

2. Authenticate with providers (one-time)

3. Provision resources and generate .env

vibe.yaml

Supported Providers

Output Targets

Environment-Specific Config

MCP Server (AI Agent Integration)

Setup

Available Tools

Example Flow

Idempotency

How It Works

Examples

Development

License