Any other AI tool, over MCP.
Any tool that speaks the Model Context Protocol can connect to Stable Baseline. Here are the details it needs, in the shapes different tools expect.
The details
| Address | https://api.stablebaseline.io/functions/v1/cloud-serve/mcp |
| Transport | Streamable HTTP (requests are sent with POST) |
| Sign-in | OAuth 2.1: the tool can register itself and opens your browser to sign in |
| Or a key | An API key, sent as Authorization: Bearer sta_... or x-api-key |
Leave out the key and a tool that supports OAuth signs you in instead. Create one under Organisation settings, Developers, API keys. See Setup.
Config shapes
mcpServers with url
Used by Cursor and similar tools. Claude Code's .mcp.json adds "type": "http".
{
"mcpServers": {
"sb": {
"url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
"headers": { "Authorization": "Bearer ${env:STABLE_BASELINE_API_KEY}" }
}
}
}servers
Used by VS Code.
{
"servers": {
"sb": { "type": "http", "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" }
}
}serverUrl
Used by Antigravity and by the Cascade agent in Devin Desktop.
{
"mcpServers": {
"sb": { "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" }
}
}httpUrl
Used by Gemini CLI.
{
"mcpServers": {
"sb": { "httpUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" }
}
}TOML
Used by Codex.
[mcp_servers.sb] url = "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" bearer_token_env_var = "STABLE_BASELINE_API_KEY"
mcp with type remote
Used by OpenCode.
{
"mcp": {
"sb": { "type": "remote", "url": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp" }
}
}A local bridge
For a tool that can only start local servers, run a small bridge that forwards to Stable Baseline. It needs Node.js:
{
"mcpServers": {
"sb": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"]
}
}
}Keep the key out of your files
STABLE_BASELINE_API_KEY environment variable or your tool's secret store, and refer to it from the config as shown. Never paste the key itself into a file you commit or share. Signing in with OAuth avoids keys altogether.No account yet?
Your AI tool can sign you up. Ask it to start a Stable Baseline sign-up: it shows you a short code and a link, you confirm in your browser, and the tool carries on with your new account. See the sign-up tools.
Document a repository
If your tool offers MCP prompts as commands, run sb-setup. Otherwise ask 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.
Checks the connection
It confirms it can reach Stable Baseline with your key or sign-in.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.Remembers them
It writes their ids to .sb/config.json, and keeps .sb/ out of git.Checks for existing docs
If the project already has documentation, it asks whether to add to it, replace it, or stop.Reads the repository
It works through the code to understand what is there.Designs a structure
Folders and documents that fit this repository, not a fixed template.Writes it
Folders, documents, and the diagrams each document needs.Updates AGENTS.md
It adds a Stable Baseline section with rules for keeping the docs current, and keeps everything else in the file.Sums up
It tells you what it created.
Keeping docs current
sb-update to record the decisions from the conversation.