VS Code with Stable Baseline.

Quickest path · Have your AI agent do it

Already have Copilot Chat (or Roo Code / Cline) open in agent mode? Paste the prompt below into the chat. The agent runs the device-code signup against Stable Baseline's anonymous-callable endpoint, shows you a 6-character code to authorise in your browser, then writes .vscode/mcp.json with the resulting API key. You never copy a key by hand.

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": "VS Code Copilot", "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 .vscode/mcp.json in the workspace root:
   {"servers": {"sb": {"type": "http", "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp", "headers": {"Authorization": "Bearer <YOUR_KEY>"}}}}

4. Tell me to reload the MCP server (Cmd/Ctrl+Shift+P → "MCP: Reload Server" or restart VS Code). Then ask what I want to do next.

Once the agent finishes step 4 and you reload, ask Copilot Chat anything that benefits from Stable Baseline tools, for example “list my Stable Baseline workspaces” to verify the connection, or jump straight to “document this codebase”.

Step 1 · Install in VS Code (manual alternative)

Skip the config file. Click the button below and VS Code opens a confirmation panel with the server pre-filled. It will prompt you for your API key. Paste your sta_… key once and it gets stored in the secure credential store, never on disk.

Step 2 · Create your API key

If you don't have an API key yet:

• Sign in to app.stablebaseline.io and open your project
• Open Project Settings (the gear icon)
• Navigate to MCP Setup → API Keys
• Click Create API Key, name it (e.g. “VS Code Atlas”)
• Copy the sta_… key (shown once only)

Project-scoped vs organisation-wide keys

Project-scoped keys follow least-privilege: each dev project gets its own key, scoped to just that project's workspace. Full API key docs →

Or configure manually

Prefer editing files directly? Create a .vscode/mcp.json in your project root:

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

Workspace vs user config

Step 3 · Verify the connection

• Open the Output panel (Ctrl+Shift+U / ⌘+Shift+U)
• Select MCP: sb from the dropdown (or GitHub Copilot Chat: MCP if using Copilot)
• Confirm Connection state: Running appears with a tool count of 180

Step 4 · Generate your documentation

Open GitHub Copilot Chat (Ctrl+Alt+I / ⌘+Alt+I) and run the setup prompt:

/mcp.sb.sb-setup

VS Code asks for prompt parameters (like project_goal) in an input bar at the top. You can type a short goal or press Enter for defaults. Pick either Insert as text or Run as Command and the agent begins onboarding your project.

What sb-setup does, in order

• Verifies the MCP connection: if it can't connect, it tells you exactly what to fix and waits for you to say “continue”
• Resolves your workspace & project: if you have multiple, it asks you to pick. If none, it links you to the app
• Creates .sb/config.json: caches your workspace and project IDs locally
• Checks for existing documentation: if docs exist, asks whether to augment, replace, or cancel
• Analyses your repository: tech stack, architecture, dependencies, security model, infrastructure, domain context
• Designs a bespoke documentation structure: no template. Tailored to your repo's natural boundaries
• Creates the documentation: real content with diagrams, not stubs
• Generates AGENTS.md: file-pattern-to-document mappings specific to your codebase
• Provides a summary: tree view of everything created, with next steps

How auto-sync works

The AGENTS.md generated in step 4 contains a table mapping your repo's file patterns to Stable Baseline documents:

These patterns are specific to your repo. When Copilot's agent changes files matching a pattern, it knows which doc to update, and does so automatically via the MCP tools.

File structure

your-project/
├── .vscode/
│   └── mcp.json          # MCP server config (step 1)
├── .sb/
│   └── config.json       # Project IDs (auto-generated)
├── AGENTS.md             # Cross-IDE auto-sync rules (auto-generated)
└── ...

All files are safe to commit. The API key is never stored in any config file. VS Code resolves it at runtime from its secure credential store. Add .sb/ to .gitignore if you prefer to keep IDs local.

Try it

Once setup has run, here are some prompts worth pasting into Copilot Chat:

Other prompts available