fortrabbit

fortrabbit for coding agents

Source: https://www.fortrabbit.com/agents Published: 2026-10-26

Steps for a coding agent to connect to fortrabbit, leave the sign-in to the person, and host, deploy and debug PHP apps.

This page is for a coding agent. The person you work for wants to host a PHP app on fortrabbit, or already does. Follow the steps in order and skip any step that is done.

1. What fortrabbit is

fortrabbit is managed PHP cloud hosting for Laravel, Craft CMS, Statamic, Kirby, WordPress, Symfony and plain PHP. People manage it in a dashboard, agents over an MCP server, the frbit CLI and SSH.

2. Ask before installing

Tell the person what you are about to install and why, then wait for a yes.

3. Connect

If the fortrabbit MCP tools are available, get_you among them, go to step 5.

With a shell, install the CLI and let it set up the agent:

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

The script installs frbit to ~/.local/bin and runs frbit setup agent. Add ~/.local/bin to the PATH if the shell cannot find frbit. With Homebrew instead: brew install fortrabbit/tap/frbit, then frbit setup agent. With npm: npm install --global @fortrabbit/cli.

frbit setup agent detects Claude Code and Codex, registers the fortrabbit MCP server with each and installs the fortrabbit agent skill. Restart the session if the client asks for it. GitHub Copilot is not detected: install the skill with frbit skills install --agent copilot.

Other MCP clients connect to https://mcp.fortrabbit.com/mcp (streamable HTTP, OAuth). Setup per client: MCP docs.

Without a shell, in claude.ai or Claude Desktop: ask the person to add a custom connector under Settings → Connectors with the URL https://mcp.fortrabbit.com/mcp, then to start a new chat.

4. Sign-in is the person's step

The first fortrabbit MCP call opens a browser page. Tell the person it is their step: they sign up with GitHub, Google, GitLab or an e-mail address, or sign in, verify the e-mail address and approve the connection.

The CLI signs in separately. Run frbit auth login --json in the background, add --signup when the person has no account, and show them the URL and the code it prints. Continue with next from its last line.

Never ask for an e-mail address, a password or a token in the chat.

5. Check the account

Call get_you and follow next, an object {step, instruction, url}, until step is ready:

• connect_git: the person connects GitHub and grants the fortrabbit GitHub App access to the repository. Give them next.url.
• add_payment_method: give them next.instruction and next.url. Never take card or payment details in the chat.

After each browser step, call get_you again instead of waiting for the person to type "done". client: true marks a client account, which cannot create environments.

6. Mental model

• An app (ap-xxxxxx) is one project. It holds one or more environments.
• An environment (en-xxxxxx), production or staging for example, deploys one branch of a GitHub repository. It answers on https://<env>.<region>.frbit.app and takes SSH at <env>@ssh.<region>.frbit.app. Its database name and user are the environment ID.
• Components are the parts of an environment that are billed by the day: PHP, MySQL, storage, jobs. Sizes and prices come from list_component_plans.
• A deployment (dp-xxxxxx) starts on every push to the connected branch.

Never guess an ID, a region, a plan size or a software version. Look it up with the list_* tools or the CLI.

7. Core operations

Task	MCP tool	frbit CLI	Other
Account, apps, environments, deployments, domains	get_you, list_*, get_*	frbit <group> list or get, with --json
Find the environment of this repository	list_git_repositories, get_app, list_environments	frbit apps list --json	git remote get-url origin
Create an app or an environment	create_app, create_environment	frbit apps create, frbit environments create
Environment variables	get_environment, update_environment	frbit environments variables get or update
Deploy		frbit environments deploy <env>	git push to the connected branch
Why a deployment failed	get_deployment, get_deployment_logs	frbit deployments logs <dp>
Restart		frbit environments restart <env>
Remote commands, database, files			ssh, mysql, rsync

Run frbit <group> --help rather than guessing a subcommand.

8. Ask before

Show the exact tool call or command and wait for a yes before:

• creating anything billed: show name, region, software, components and the monthly price first
• writing environment variables
• deploying, restarting or changing anything on a production environment
• a database push or pull, or rsync to or from an environment
• deleting anything: say what will be lost, then wait for a clear yes in the person's next message

9. Close

Tell the person:

• the live URL, https://<env>.<region>.frbit.app
• the dashboard link, https://dash.fortrabbit.com/environments/<env>
• the end of the free trial, when get_app reports one, and that a payment method keeps the app online after it: https://dash.fortrabbit.com/new/payment-method

10. Reference

• www llms.txt and docs llms.txt. Every docs page is Markdown under /raw/<path>.md.
• Automation docs: MCP server, CLI, public API, agent skills
• Agent skills index and source
• Public API reference
• Status page