Workflows

Client recipes

Stable Baseline speaks MCP, so any compliant client can read and write your workspace. These are the copy-paste configs for the clients we test against — pick yours, or use the generic recipe for anything else.

Set up auth first

Every recipe assumes you already have a connection. Head to Setup & auth to mint an API key or authorise over OAuth, then come back and pick your client. The tools themselves are identical across every recipe — see the tools reference.

Pick your client

Each recipe covers the config file, how auth is passed, and the workflow that client is best at. If yours is not listed, generic almost certainly works.

Claude Code

CLI and desktop. OAuth connector plus the /sb-* slash-commands for onboarding and sync.

Cursor

mcp.json config, project rules, and the doc-per-surface mapping for a Cursor workspace.

Windsurf

Cascade config and the workflow for keeping AGENTS.md in step with your docs.

OpenCode

Server config plus the file-to-document mapping OpenCode agents use.

Warp

Warp's MCP panel, auth, and the terminal-first workflow.

OpenAI Codex

config.toml for the Codex CLI, including headers-based auth.

Antigravity

Connector setup for Google's agent-first IDE.

VS Code

GitHub Copilot agent mode, plus the /mcp.sb.* prompt commands it exposes.

ChatGPT

Developer-Mode custom connector, OAuth consent, and per-organisation connections.

Gemini

Gemini CLI, Extensions, and the web app connector.

Any other MCP client

The generic recipe: server URL, Bearer auth, and the config shapes most clients accept.

Setup & auth

API keys, OAuth, and connecting to the right organisation.

Permissions

Scope a connection to a workspace, project, or folder.