Recipe

VS Code with Stable Baseline.

Add Stable Baseline to VS Code for GitHub Copilot's agent mode, and other extensions that use VS Code's MCP servers. Sign in once, then document your repository with sb-setup.

1. Install

Install in VS Code

Adds the Stable Baseline server. VS Code asks you to sign in the first time it connects.

Or add it by hand to .vscode/mcp.json in your repository, or to your user configuration with the MCP: Open User Configuration command:

.vscode/mcp.jsonjson
{
  "servers": {
    "sb": {
      "type": "http",
      "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"
    }
  }
}

For organisations on GitHub Copilot Business or Enterprise

Your GitHub administrators need to allow MCP servers in Copilot before any server, Stable Baseline included, can be used.

Or use an API key

Create one under Organisation settings, Developers, API keys. See Setup. With this config VS Code asks for the key once and keeps it in its secure store, so the key never sits in the file:

.vscode/mcp.jsonjson
{
  "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}"
      }
    }
  }
}

To change the stored key, hover the ${input:sb-api-key} reference in the file and choose to edit or clear it.

Check it works

  • Open Copilot Chat in agent mode and open the tools picker: the sb tools are listed.
  • A chat request can use up to 128 tools at once. If you have many servers, turn off the tool groups you do not need in the picker.
  • If something looks stuck, run MCP: List Servers and restart sb.

2. Document the repository

In Copilot Chat, type /mcp.sb.sb-setup and say what you want, for example “architecture docs for new engineers”. It then:

  1. Checks the connection

    It confirms it can reach Stable Baseline with your key or sign-in.
  2. Finds your workspace and project

    It never creates them: if it cannot find the ones you mean, it asks you to create them in the app first.
  3. Remembers them

    It writes their ids to .sb/config.json, and keeps .sb/ out of git.
  4. Checks for existing docs

    If the project already has documentation, it asks whether to add to it, replace it, or stop.
  5. Reads the repository

    It works through the code to understand what is there.
  6. Designs a structure

    Folders and documents that fit this repository, not a fixed template.
  7. Writes it

    Folders, documents, and the diagrams each document needs.
  8. Updates AGENTS.md

    It adds a Stable Baseline section with rules for keeping the docs current, and keeps everything else in the file.
  9. Sums up

    It tells you what it created.

Every Stable Baseline prompt appears the same way, as /mcp.sb. followed by its name. See the full list.

3. Try it

  • “What changed in the checkout service this week? Update its document.”
  • “Add a sequence diagram of the sign-in flow to the authentication document.”
  • “Create a plan for the database migration with three phases.”
  • “Log a risk in the work register: the payment provider's rate limits.”