# Agent setup

Source: https://docs.fortrabbit.com/platform/automation/agents
Published: 2026-08-24
Updated: 2026-10-27
Reviewed: 2026-10-23

> Connect Claude Code, Codex, Cursor or another coding agent to fortrabbit with one command, and pick between MCP server, CLI, agent skills and API.


## Get set up

One command installs the frbit CLI, the agent skills and the MCP server for Claude Code and Codex:



```shell
curl -fsSL https://www.fortrabbit.com/agents.sh | sh
```

With the CLI in place, `frbit setup agent` does the same. Add `--agent codex` to set up one agent only.

Any other agent can set itself up. Paste this prompt:



```txt
Read https://www.fortrabbit.com/agents.md and set up fortrabbit.
```

claude.ai, Cursor, VS Code and other MCP clients take the MCP server URL: `https://mcp.fortrabbit.com/mcp`. The commands per client are on the [MCP server](/platform/automation/mcp#connect-an-agent) page.

On the first request, the agent opens a browser page. Sign in or sign up there and approve the connection. The agent never sees a password.

## Choose the tool

| Tool                                                         | What it is                    | Authentication       |
| ------------------------------------------------------------ | ----------------------------- | -------------------- |
| [MCP server](/platform/automation/mcp)            | Remote endpoint for AI agents | Browser sign-in      |
| [CLI](/platform/automation/cli)                   | `frbit` binary, client of API | Browser or API token |
| [Agent skills](/platform/automation/agent-skills) | Workflow instructions         | Nothing of their own |
| [Public API](/platform/automation/api)            | REST interface over HTTP      | Personal API token   |

- **MCP server**: the agent reads apps, environments and deployments, and creates apps and environments.
- **CLI**: the agent, a script or a CI job deploys, restarts, reads logs and sets environment variables.
- **Agent skills**: the agent follows the fortrabbit workflows for deployments, database sync and SSH. They hold no credentials and open no connection.
- **Public API**: a tool of your own talks to the platform. The CLI is built on it.

The setup command above installs the first three. The API needs no setup beyond a token.

## Browser sign-in or API token

A person at their own computer signs in through the browser: `frbit auth login` for the CLI, the client's own login for MCP. Anything that runs without a person present, such as a CI job, a server or an integration, takes a personal API token.

|           | Browser sign-in                | API token           |
| --------- | ------------------------------ | ------------------- |
| Created   | `frbit auth login`, MCP client | Dashboard           |
| Expires   | After 30 days unused           | Never               |
| Access    | Fixed per client               | Chosen at creation  |
| Revoke at | `AI agents`                    | `API tokens`        |

An MCP client without OAuth support takes a personal API token as a bearer credential instead of the browser sign-in.

---

- [MCP server](/platform/automation/mcp)
- [CLI](/platform/automation/cli)
- [Agent skills](/platform/automation/agent-skills)
- [Public API](/platform/automation/api)