AI-Powered Project Setup

Eden Stack is the first template designed for AI-native development. Instead of manually creating accounts, copying API keys, and configuring services, you describe what you want and Claude Code sets it up for you.

The Problem with Traditional Setup

Setting up a full-stack app typically requires:

1. Create a database on Neon → Copy connection string
2. Create Stripe account → Set up products → Copy API keys
3. Create Resend account → Verify domain → Copy API key
4. Create PostHog project → Copy API key
5. Create Sentry project → Copy DSN
6. Create Cloudflare R2 bucket → Generate access keys
7. Manually paste all 15+ values into .env

Time: 30-60 minutes of clicking and copying.

The Eden Stack Way

"Set up my Eden Stack project using eden.setup.json"

Time: 5 minutes. One prompt.

How It Works

Eden Stack uses Model Context Protocol (MCP) servers that let AI assistants interact directly with external services.

Quick Start

1. Create Your Config

cp eden.setup.example.json eden.setup.json

Edit with your project details:

{
  "project": {
    "name": "my-saas",
    "domain": "my-saas.com"
  },
  "services": {
    "database": { "provider": "neon", "region": "aws-us-east-1" },
    "payments": {
      "provider": "stripe",
      "products": [
        { "name": "Pro", "price": 2900, "interval": "month" }
      ]
    },
    "email": { "provider": "resend" },
    "storage": { "provider": "cloudflare-r2" },
    "analytics": { "provider": "posthog" },
    "errors": { "provider": "sentry" }
  }
}

2. Authenticate Services

# GitHub CLI
gh auth login
 
# Neon
npx neonctl auth

Other services (Stripe, Cloudflare, PostHog, Sentry) authenticate via OAuth popup when first used.

3. Run Setup in Claude Code

Open Claude Code and say:

Set up my Eden Stack project using eden.setup.json

Claude will:

• Read your configuration
• Create resources on each service via MCP
• Collect all credentials
• Generate your .env file

Available MCP Servers

MUST HAVE (Core Functionality)

SHOULD HAVE (Production-Ready)

Declarative Configuration

The eden.setup.json config is validated against a JSON Schema. You define what you want, the AI figures out how to create it.

Example: Different Pricing Tiers

{
  "services": {
    "payments": {
      "products": [
        {
          "name": "Starter",
          "price": 0,
          "interval": "month",
          "features": ["100 requests/month", "Community support"]
        },
        {
          "name": "Pro",
          "price": 2900,
          "interval": "month",
          "features": ["Unlimited requests", "Priority support"]
        },
        {
          "name": "Enterprise",
          "price": 9900,
          "interval": "month",
          "features": ["Everything in Pro", "Custom integrations", "SLA"]
        }
      ]
    }
  }
}

The Stripe MCP will create all three products with their prices and feature lists.

Why This Matters

1. Reproducible — Same config, same setup every time
2. Self-Documenting — Config file shows exactly what services you use
3. Fast — 5 minutes vs 60 minutes
4. Error-Free — No typos in API keys, no missed steps
5. Onboarding — New team members run one command

Future: Any AI Editor

While currently optimized for Claude Code, the MCP servers work with any MCP-compatible client:

• Cursor
• VS Code with Copilot
• Claude Desktop
• Any future AI coding tools

Next Steps

• Getting Started - Full setup guide
• Background Jobs - Using Inngest
• Stripe Payments - Payment integration