Any MCP-Compatible IDE

What You'll Get

Step 1: Add the MCP Server

Before you begin, you'll need a Stable Baseline API key. Visit the MCP Setup Guide to create one from your workspace settings.

Choose the configuration format that matches your IDE:

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

{
  "servers": {
    "stablebaseline-mcp": {
      "type": "http",
      "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

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

[mcp_servers.stablebaseline-mcp]
url = "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"
bearer_token_env_var = "STABLE_BASELINE_API_KEY"
http_headers = {}
enabled = true

claude mcp add stablebaseline-mcp \
  --transport http \
  --url "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" \
  --header "Authorization: Bearer YOUR_API_KEY"

mcp:
  stablebaseline-mcp:
    type: remote
    url: https://api.stablebaseline.io/functions/v1/cloud-serve/mcp
    headers:
      Authorization: Bearer YOUR_API_KEY

{
  "mcpServers": {
    "stablebaseline-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Step 2: Generate Your Documentation

Once the MCP server is connected, open your IDE's AI chat/agent and type:

Run the sb-setup prompt from the stablebaseline-mcp server

The AI agent will walk you through an interactive setup process to generate documentation for your project.

What it does

The sb-setup prompt runs a 9-step process:

1. Verifies MCP Connection — Confirms the Stable Baseline server is reachable and authenticated
2. Resolves Workspace & Project — Finds or creates your Stable Baseline workspace and project
3. Scans Your Codebase — Analyzes project structure, tech stack, dependencies, and architecture
4. Checks for Existing Docs — Detects if documentation already exists in Stable Baseline and offers to augment, replace, or cancel
5. Creates Folder Structure — Organizes documentation into logical folders matching your codebase
6. Generates Documents — Writes comprehensive docs for each area of your codebase
7. Adds Diagrams — Creates architecture and flow diagrams using Mermaid, PlantUML, or other supported formats
8. Configures AGENTS.md — Adds auto-sync rules to your project's AGENTS.md file (augments existing content — never removes what's already there)
9. Summary & Next Steps — Provides a summary of everything created with links to view in Stable Baseline

What Gets Documented

The exact documentation 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 will contain rules that tell your AI agent when to update documentation.

Whenever your AI agent modifies files matching these patterns, it will automatically update the corresponding Stable Baseline documentation using 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.

Keep Docs Updated Mid-Conversation

After making significant changes during a coding session — architectural decisions, new features, schema changes, key refactors — your agent will typically automatically propose updates to your documentation via the sb-update prompt based on the rules in your AGENTS.md file. Wait for the agent to finish its current coding step, and it will often follow up by running sb-update.

However, you can also manually capture everything in your documentation without leaving the conversation:

Run the sb-update prompt

The sb-update prompt scans the current conversation context, identifies what changed, maps changes to existing documents, and applies targeted patches.

Try It

Once setup is complete, try these example prompts in your IDE's AI agent:

Regenerate Documentation

To regenerate your entire documentation from scratch:

Run the sb-setup prompt from the stablebaseline-mcp server

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

MCP Compatibility

Stable Baseline's MCP server uses the Streamable HTTP transport and supports:

Other Prompts Available