Windsurf with Stable Baseline.

Quickest path · Have Cascade do it

Already running Windsurf with Cascade in this repo? Paste the prompt below. Cascade runs the device-code signup against Stable Baseline's anonymous-callable REST endpoint, shows you a 6-character code to authorise in your browser, then writes ~/.codeium/windsurf/mcp_config.json with the resulting API key.

I want to onboard to Stable Baseline using its agent-driven signup. Walk me through end-to-end without stopping in between.

1. POST https://api.stablebaseline.io/functions/v1/cloud-serve/api/v1/tools/startSignup
   Body: {"agent_label": "Windsurf", "intent": "mcp_setup"}
   Response: {user_code, verification_url, device_code, poll_interval_seconds, ...}
   Show me user_code and verification_url. Tell me to open the URL, sign in or sign up, paste the code, click Authorize.

2. Every 5 seconds, POST https://api.stablebaseline.io/functions/v1/cloud-serve/api/v1/tools/pollSignupStatus
   Body: {"device_code": "<from step 1>"}
   Stop when status is "authorized" — response includes api_key (starts with sta_). If denied or expired, tell me and stop.

3. Write ~/.codeium/windsurf/mcp_config.json with the api_key inline. Note Windsurf uses "serverUrl" (NOT "url") for remote HTTP servers:
   {
     "mcpServers": {
       "sb": {
         "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
         "headers": {"Authorization": "Bearer <YOUR_KEY>"}
       }
     }
   }
   If the file exists, MERGE the mcpServers block — don't overwrite other keys.

4. Tell me to reload Windsurf's MCP — Windsurf Settings → MCP and toggle the "sb" server, or restart Windsurf. Then ask what I want to do next.

Before you begin

You'll need a Stable Baseline API key. Visit the MCP setup guide to create one from your workspace settings. Keys are prefixed sta_… and shown only once.

Step 1 · Option A: via Windsurf's settings UI

• Open Windsurf settings (⌘, on macOS, Ctrl+, on Windows/Linux)
• Navigate to Cascade → MCP Servers
• Click Add Server and select Raw JSON
• Paste the configuration below

{
  "mcpServers": {
    "sb": {
      "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your actual Stable Baseline API key.

Step 1 · Option B: edit the config file directly

Open the MCP config file at:

• macOS / Linux: ~/.codeium/windsurf/mcp_config.json
• Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Prefer keeping your key in an environment variable instead of the file? Windsurf supports interpolation via the ${env:VAR_NAME} syntax:

{
  "mcpServers": {
    "sb": {
      "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
      "headers": {
        "Authorization": "Bearer ${env:STABLE_BASELINE_API_KEY}"
      }
    }
  }
}

Set STABLE_BASELINE_API_KEY in your shell profile and restart Windsurf. You should see the Stable Baseline server listed with a connected status.

Step 2 · Generate your documentation

Once the server is connected, open Cascade and paste the setup prompt:

Run the sb-setup prompt from the sb server

Cascade walks you through an interactive setup process to generate documentation tailored to your project.

What sb-setup does — the 9-step process

• Verifies MCP connection — Confirms the Stable Baseline server is reachable and authenticated
• Resolves workspace & project — Finds or creates your Stable Baseline workspace and project
• Scans your codebase — Analyses project structure, tech stack, dependencies, and architecture
• Checks for existing docs — Detects if documentation already exists in Stable Baseline and offers to augment, replace, or cancel
• Creates folder structure — Organises documentation into logical folders matching your codebase
• Generates documents — Writes comprehensive docs for each area of your codebase
• Adds diagrams — Creates architecture and flow diagrams using Mermaid, PlantUML, or other supported formats
• Configures AGENTS.md — Adds auto-sync rules to your project's AGENTS.md file (augments existing content — never removes what's already there)
• Summary & next steps — Provides a summary of everything created with links to view in Stable Baseline

What gets documented

• Architecture — High-level system design, component relationships, data flow
• API & Integrations — Endpoints, external services, authentication flows
• Data Model — Database schemas, relationships, migrations
• Frontend — Component hierarchy, state management, routing
• Backend — Server logic, middleware, business rules
• DevOps — Build pipeline, deployment, environment configuration
• Auth & Identity — Authentication, authorisation, user management

The exact structure is determined dynamically based on your codebase — no two projects get the same output.

How auto-sync works

After setup, your AGENTS.md file contains rules that tell Cascade when to update documentation:

Whenever Cascade modifies files matching these patterns, it automatically updates the corresponding Stable Baseline documentation via the sb-sync prompt.

File structure

Your Stable Baseline Project
├── Architecture/
│   ├── High Level Overview
│   └── System Architecture Diagram
├── Frontend/
│   ├── Component Hierarchy
│   ├── State Management
│   └── Routing & Navigation
├── Backend/
│   ├── API Endpoints
│   ├── Business Logic
│   └── Middleware & Auth
├── Data Model/
│   ├── Database Schema
│   └── Entity Relationships
└── DevOps/
    ├── Build & Deploy
    └── Environment Config

This is an example. Your actual structure will be tailored to your specific project.

Try it

Once setup is complete, try these prompts in Cascade:

Regenerate documentation

To regenerate your entire documentation from scratch:

Run the sb-setup prompt

Setup will detect existing documentation and ask whether you want to augment (add to existing), replace (start fresh), or cancel.

Other prompts available