Skip to content
Toado Docs

Quickstart

The full quickstart in video form. Same five steps as the page below.

This is the five-minute path: connect Claude Code to Toado via OAuth, point it at a project, and ask it to fix a ticket. If anything trips you up, jump to Troubleshooting.

1. Connect Claude Code to Toado

Two steps. Register the server, then authenticate from inside a session.

1. Register. In your terminal — bash, zsh, PowerShell, or cmd all work:

Terminal window
claude mcp add toado --transport http https://mcp.toado.dev/mcp --scope user

--scope user makes Toado available across all your projects, not just the current one.

2. Authenticate. Open a Claude Code session (in VS Code or Cursor, the Claude Code chat panel; in a terminal, run claude) and type:

/mcp

Claude Code opens your browser. Sign in with the same account you use for the web app. The consent screen offers three access levels, Read-only, Read + comment, or Full access. Pick Full access for first-time setup so the agent can fix tickets end to end. Click Authorize, the tab closes, and Claude Code is connected.

No tokens to copy, no config files to edit. The OAuth flow issues a scoped credential automatically and stores it securely in Claude Code.

2. Verify the connection

In Claude Code, ask:

List my Toado companies.

Claude should call list_companies and return your company list. If it does, you are connected. If it does not, see Troubleshooting.

3. Point Claude at a project

Ask Claude to find the project you want it to work on:

Find my Toado project for "acme web". Show me the To Do column.

Claude will call list_projects, list_columns, then list_tickets filtered to the To Do column.

4. Fix your first ticket

Ask Claude to grab the ticket and start work:

Get the top ticket from To Do, read its capture and DevTools context, then start work on it.

Under the hood Claude will:

  1. get_ticket to fetch the title, description, screenshot URL, console, network, errors, and annotations.
  2. get_capture_asset to download the screenshot (so it can see the visual bug).
  3. start_work_on_ticket to record a git branch name on the ticket.
  4. Read your code, make changes, post an add_comment describing what it did.
  5. move_ticket to In Review (or wherever your skill sends it).

You will see Claude’s comment in the ticket detail with an MCP badge that distinguishes it from human comments.

5. Work the whole queue (next step)

Once one ticket succeeds, scale up. The recommended pattern is to install the toado-triage skill and tell Claude:

/toado-triage acme web

The skill walks the To Do column ticket by ticket, applies a consistent fix-comment-move loop, and reports progress.

Alternative: manual token

OAuth covers almost every case. Reach for a manually-issued token only if one of these applies:

  • Your client does not support OAuth (Cline, Continue, Goose, Zed, custom SDK builds).
  • You are wiring Toado into CI or another non-interactive context where a browser-based OAuth flow does not fit.
  • You need a token scoped down to specific companies or projects, or restricted to read-only.
  • You are running a self-hosted Toado backend.

Create a token

In the Toado web app:

  1. Open Settings › API tokens.
  2. Click New token.
  3. Label it specifically, e.g. claude-code on macbook or ci-pipeline. The label shows up on every comment and edit the token makes, so make it scannable.
  4. Choose scopes. For a full-power agent, pick all four: read, comments, tickets:write, tickets:assign. For read-only audits, just read.
  5. Optionally restrict to one company or project.
  6. Click Create. The token appears once. Copy it now: tok_01HXYZ…. You cannot retrieve it again.

See Tokens & scopes for the full scope matrix.

Register the MCP server with the token

Pick the install path that matches your client. The hosted endpoint (https://mcp.toado.dev/mcp) is the same one the OAuth flow uses; the token is passed as a Bearer header instead of doing the OAuth dance.

One-line install with a manually-issued token:

Terminal window
claude mcp add toado --url https://mcp.toado.dev/mcp \
  --header "Authorization: Bearer tok_paste_your_token_here"

Replace tok_paste_your_token_here with the token you generated under Settings › API tokens. See Tokens & scopes. Most users do not need this; OAuth via the per-client flows in Installation is simpler and the recommended path.

Restart Claude Code (or the host app) so it loads the new MCP server. Then jump back to step 2 above to verify and start fixing tickets.