Command line
Sign in with the Rindler CLI
The rindler CLI signs you in from the terminal, mints a temporary key tied to your Rindler account, and installs the Rindler MCP into Claude Code and Codex for you. Nothing to copy or paste, and no key to revoke by hand.
Install and sign in
Install the CLI, then sign in:
curl https://rindler.ai/cli | sh
rindler login
rindler login opens your browser to sign in with your Rindler account over OAuth 2.0 with PKCE, then mints a temporary key bound to your session and installs the Rindler MCP into Claude Code and Codex. On a headless box, over SSH, or when your browser is on another machine, run rindler login --paste: it prints a URL you can open anywhere, and you paste back the short code it shows.
What it configures
The CLI writes the Rindler MCP server into each agent's config and leaves your other servers untouched.
| Agent | File | Entry |
|---|---|---|
| Claude Code | ~/.claude.json | mcpServers.rindler (HTTP + your key) |
| Codex | ~/.codex/config.toml | [mcp_servers.rindler] |
One combined key covers both reading and acting on supported sites and, if your workspace is entitled, mapping new sites. Re-run rindler mcp install any time, rindler status shows what is configured, and rindler logout revokes the key and removes the entries.
Keys expire with your session
The key the CLI mints is bound to your Rindler sign-in. It stops working when you sign out everywhere or the session ends, and it rolls forward while you keep using it, so active use keeps you signed in without reopening the web app. When it lapses, run rindler login again to renew.
For CI or a headless service, set RINDLER_API_KEY to a long-lived key from the dashboard instead. The CLI reads it at the highest precedence and never writes it to disk.
Where to go next
- New to Rindler? Start with the quickstart to connect an agent.
- For the full tool surface once you are connected, see the docs overview.