CLI

Install the Tada CLI, sign in from a laptop or from CI, check that a session is alive, and start the MCP server your agent talks to.

The tada-mcp package installs two names for one program, tada and tada-mcp. The CLI puts credentials on your machine and starts the MCP server. Your agent proves a feature through the verify_feature tool.

Install

npmpnpmyarnbun

npm install -g tada-mcp

pnpm add -g tada-mcp

yarn global add tada-mcp

bun add -g tada-mcp

Commands

Command	What it does
`tada login`	Signs in through your browser. Nothing is typed or pasted.
`tada login --key <key>`	Saves an API key, for CI and headless machines.
`tada key <key>`	Saves an API key directly.
`tada whoami`	Asks the server who you are. Exits non-zero when the session is dead.
`tada status`	Shows the credentials on this machine, then checks them with the server.
`tada logout`	Removes the stored credentials.
`tada`	Starts the MCP server on stdio.
`tada --version`	Prints the version and nothing else.
`tada --help`	Prints the command list.

On your own machine

tada login

This opens your browser. You press Authorize in a browser where you are already signed in to Tada, and the CLI stores a key in ~/.tada/.

On CI or a headless machine

Create a key in Settings > CLI & API keys, then save it:

tada login --key tada_sk_…

The key can also arrive as an argument to tada key, from a prompt in a terminal, or piped on stdin:

echo "$TADA_API_KEY" | tada key

Tada checks the key with the server before it reports success, so a mistyped or revoked key fails now, not in the middle of a CI job.

Check the session

tada whoami asks the server and exits non-zero when there is no valid session. Use it in scripts, the way you would use gh auth status.

tada status is the fuller report: which credentials are on this machine, and whether the server accepts them. A credentials file on disk can be expired or revoked and still look fine, so status always asks the server.

Version

tada --version

It prints the bare version, such as 0.1.49, so a script can compare it directly.

Environment

Variable	Default	Purpose
`TADA_API_URL`	`https://api.taada.dev`	Points the CLI at a different API. You need this only when you run one yourself.

Notes

There is no upload command. Tada films the walk itself, so it can check it worked. A video made somewhere else cannot be published as a Tada film.
Unknown commands fail. tada upload prints the usage and exits 1, so a wrong command never looks like success.