Install and connect

Install the CLI, sign in, and give your coding agent the verify_feature tool — about two minutes.

Tada opens your app in a real browser, walks a flow end to end, and hands you one shareable link. This page sets up the path you drive from your editor: your coding agent asks for the run, so you never hit record.

For runs that happen on their own — on every preview deploy, with the merge waiting on the result — start with flows instead.

1. Install the CLI

Tada ships as a single global CLI, like supabase or railway:

npm i -g tada-mcp

2. Log in

This opens your browser to authorize. No password in the terminal:

tada login

On CI or a headless box there’s no browser to open, so use a personal API key from taada.dev/settings instead:

tada login --key tada_sk_…

3. Connect your agent

Add Tada to Claude Code (or Cursor) as an MCP server:

claude mcp add tada -- npx tada-mcp

Every other client takes the same mcpServers block: Cursor, VS Code, Windsurf, Zed, Codex. Drop this into whichever config file yours uses:

{
  "mcpServers": {
    "tada": {
      "command": "npx",
      "args": ["-y", "tada-mcp"]
    }
  }
}

Your agent now has a new tool, verify_feature. You never call it yourself. See the verify_feature reference for what it takes.

4. Ask your agent to record

That’s it. Now just tell your agent:

Record a demo of the feature I just built.

A few seconds later, a shareable link shows up in your library. Send it to anyone. They watch with no login and leave comments that come back to you as work.

Check it worked at any point with:

tada whoami

Next: record your first demo.