# How an AI agent gets access to Rippit

> OAuth for MCP clients, the CLI and temporary accounts, and API tokens, with every credential kept out of the conversation.

The ways an agent can sign a person in to Rippit, or get them an account, and what each credential reaches. For the full setup, start at https://www.rippit.com/setup.md.

Never ask the person for a password, an API key or a token in the chat. Every way in below has the person approve in their own browser, or needs no person at all.

## Discover

- Authorization server: https://app.rippit.com/.well-known/oauth-authorization-server. It supports dynamic client registration and client ID metadata documents, so an MCP client registers itself.
- MCP server: `https://mcp.rippit.com/mcp`. Its protected-resource document is https://mcp.rippit.com/.well-known/oauth-protected-resource (scopes `mcp` and `offline_access`).
- Tools, readable without signing in: https://mcp.rippit.com/tools.md

## Pick a way in

| The agent | Use |
| --- | --- |
| Is an MCP client that can open a browser (Claude, ChatGPT, Cursor, VS Code, Claude Code) | OAuth when it connects to `https://mcp.rippit.com/mcp`. The client registers itself; there is no client ID or secret to set. |
| Can run shell commands | The Rippit CLI: `rippit login`, or `rippit start` for a person with no account. See https://www.rippit.com/setup.md |
| Can only make HTTP requests, with no MCP client or shell | Ask the person to connect Rippit in their agent app, from https://www.rippit.com/setup. An agent that fetched tokens itself would carry them in the conversation. |
| Is code that runs on its own, like a scheduled upload | An API token a workspace admin creates outside the chat |

## A person with no account

`rippit start` creates a temporary account at once, with no email or browser, and signs the CLI in. It is only for people with no Rippit account: one that is claimed with an email that already has an account is closed, and nothing moves across. The person keeps it by claiming it, with `rippit claim --wait`, within 14 days; an unclaimed account is then deleted. Until it is claimed it can't sign in over MCP, and some features are off. Details: https://docs.rippit.com/temporary-accounts.md

## API tokens

A workspace admin creates one with `rippit token create`, or `rippit token create --scope mcp` for an MCP client that sends a token instead of signing in. The full token is shown once. It never belongs in a chat with an agent. Details: https://docs.rippit.com/api-reference/authentication.md

## When a request is refused

- `401` from `https://mcp.rippit.com/mcp` with a `WWW-Authenticate` header: the token is missing or expired. Refresh it, or sign in again.
- `temporary_account_claimed`: the temporary account was claimed. Sign in again with `rippit login`.
- `temporary_account_closed`: the person already has a Rippit account, or joined a team that invited them, so this one was closed. Sign in with `rippit login`; don't start another temporary account.
- `temporary_account_expired`: nobody claimed the account within 14 days, so it was deleted. Run `rippit start` for a new one, or `rippit login` if the person has an account.
- `daily_limit_reached` from `rippit start`: too many temporary accounts from this network today. Use `rippit login` instead.

## Signing out

`rippit logout` signs the CLI out. `rippit token revoke <id>` revokes an API token.
