Warp with Stable Baseline.

1. Add the server

In Warp, open Settings, Agents, MCP servers, add a server, and paste:

{
  "sb": {
    "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"
  }
}

Warp opens your browser to sign in to Stable Baseline when it first connects.

Or use an API key

Create one under Organisation settings, Developers, API keys. See Setup.

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

2. Document the repository

Ask Warp's agent in plain words:

Document this repository in my Stable Baseline project. Use the Stable Baseline tools to find my workspace and project (do not create them), read the code, design a structure of folders, documents and diagrams, write them, and add a Stable Baseline section to AGENTS.md so you keep the docs current as the code changes.

It follows the same steps as the sb-setup prompt:

1. 1

   Checks the connection

   It confirms it can reach Stable Baseline with your key or sign-in.
2. 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. 3

   Remembers them

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

   Checks for existing docs

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

   Reads the repository

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

   Designs a structure

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

   Writes it

   Folders, documents, and the diagrams each document needs.
8. 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. 9

   Sums up

   It tells you what it created.

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.”