Agent setup

# Get set up

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

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:

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 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

• 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.

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