VS Code

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.

One-Click Install (Recommended)

Manual Setup (Alternative)

If you prefer manual configuration, create a .vscode/mcp.json file in your project root:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "sb-api-key",
      "description": "Stable Baseline API Key",
      "password": true
    }
  ],
  "servers": {
    "stablebaseline-mcp": {
      "type": "http",
      "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
      "headers": {
        "Authorization": "Bearer ${input:sb-api-key}"
      }
    }
  }
}

After saving, verify the connection in the Output panel (select "GitHub Copilot Chat - MCP" from the dropdown).

Step 2: Generate Your Documentation

Once the MCP server is connected, open GitHub Copilot Chat (Ctrl+Alt+I / Cmd+Alt+I) and type:

/mcp.stablebaseline-mcp.sb-setup

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 GitHub Copilot when to update documentation.

Whenever Copilot 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.

Try It

Once setup is complete, try these example prompts in GitHub Copilot Chat:

Regenerate Documentation

To regenerate your entire documentation from scratch:

/mcp.stablebaseline-mcp.sb-setup

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

Team Setup

VS Code's MCP configuration is workspace-level by default. To share the Stable Baseline setup with your team:

1. Commit the .vscode/mcp.json file to your repository
2. Each team member will be prompted for their own API key on first use (thanks to ${input:sb-api-key})
3. No secrets are ever stored in the config file

Other Prompts Available