fortrabbit-api-access

You connect an agent to fortrabbit so it can use the **MCP server** (`/mcp`) or the **Public API** (`/v1`) on the user's behalf. There are two ways in. Pick by what the user is connecting: | Situation | Path | |-----------|------| | An MCP client (Claude Code, Codex, Cursor) needs the fortrabbit MCP server | **OAuth install** — Step 1. No token, no secret handling. | | A script, CI job, or `curl` needs the `/v1` REST API | **Public API token** — Step 3. | | An MCP client with no OAuth support | **Public API token** — Step 3, configured as a Bearer header. | | The MCP server has no tool for the operation | **`frbit` CLI** — Step 5. Fall back to a token and `curl` only if the CLI cannot be installed. | Default to OAuth. Only reach for a token when OAuth cannot apply. --- ## Step 1 — Install the MCP server via OAuth (preferred) One command. The client opens a browser, the user approves, and the client stores the credentials itself. **The agent never sees, handles, or stores a token in this flow.** **Claude Code:** ```sh claude mcp add --transport http fortrabbit https://mcp.fortrabbit.com/mcp ``` **OpenAI Codex** — Codex does not publish a Client ID Metadata Document, so it must be given the client ID explicitly: ```sh codex mcp add fortrabbit --url https://mcp.fortrabbit.com/mcp --oauth-client-id https://api.fortrabbit.com/.well-known/oauth-client/codex ``` After running it, tell the user to complete the browser approval, then verify by calling the `get_you` tool — i...