mcp-stripe-projects

An MCP (Model Context Protocol) server that wraps the Stripe Projects CLI, enabling AI agents like Claude Code and cc-agent to provision infrastructure services — Vercel, Railway, Supabase, Neon, PlanetScale, Turso, Chroma, Clerk, PostHog, and Runloop — via structured tool calls instead of manual shell commands. All provisioning, env sync, and status checks happen through unified Stripe billing.

Prerequisites

1. Stripe CLI installed and authenticated:

   # macOS
   brew install stripe/stripe-cli/stripe
   
   # npm (global)
   npm install -g stripe
   
   # Authenticate
   stripe login

2. Node.js 18 or higher.

Installation

npm install -g mcp-stripe-projects

MCP Configuration

Add to your Claude Desktop claude_desktop_config.json (or any MCP-compatible client config):

{
  "mcpServers": {
    "stripe-projects": {
      "command": "npx",
      "args": ["-y", "mcp-stripe-projects"]
    }
  }
}

Available Tools

| Tool | Description | |------|-------------| | init_project | Initialize Stripe Projects in the current directory, writing agent skills files | | get_context | Get full infrastructure context (provider states, env vars, config) as a single blob for seeding agents | | list_providers | List all available providers and their status | | provision_service | Provision a new service (e.g. vercel, railway, supabase, clerk). Supports optional tier | | remove_service | Remove a provisioned service | | sync_env | Sync all provider credentials into local .env file via the Stripe credential vault | | get_status | Get current project status — provisioned providers, billing status, env sync state | | upgrade_service | Upgrade a service to a higher tier |

All tools accept an optional path parameter pointing to the project directory (defaults to cwd).

Example Agent Workflow

1. init_project({ path: "/my/app" })
   → Initializes Stripe Projects, writes .stripe/projects.json

2. get_context({ path: "/my/app" })
   → Returns full infrastructure context to seed the agent's understanding

3. provision_service({ provider: "supabase", tier: "pro", path: "/my/app" })
   → Provisions a Supabase Pro instance, stores credentials in Stripe vault

4. provision_service({ provider: "vercel", path: "/my/app" })
   → Provisions a Vercel project, links it

5. sync_env({ path: "/my/app" })
   → Writes all provider credentials to .env

6. get_status({ path: "/my/app" })
   → Returns which providers are active, billing summary, last env sync

License

MIT