fortrabbit / agents

πŸ€–

Let the agent handle the details.

Agent skills

An open source skill that teaches a coding agent how fortrabbit works. Asked in plain words, the agent deploys, syncs the database and files, runs remote commands and finds out why a site fails.

Try for free

7 days free trial

The agent runs the procedure. Reading the documentation is not the same as performing the operation correctly. The skill carries the workflows β€” finding the environment, deploying, syncing files, moving a database, running a remote command β€” so a coding agent executes them instead of reconstructing them from prose.

Plain words, no commands

"Deploy this", "pull the live database", "why does the site return a 500?". The agent finds the environment from the git remote and branch. Before anything that changes a live environment, it shows the command and waits for a yes.

With or without a connection

The skill works over SSH and rsync on its own. Adding the MCP server lets the agent list apps, open environments and read deployment logs without a shell. The two work together.

It is open source, so what an agent is being told to do can be read before it does it.

https://github.com/fortrabbit/agent-skills

Install, update and per-agent setup:

https://docs.fortrabbit.com/platform/automation/agent-skills

Different by design

Frequently asked

Which agents does it work with?
Claude Code, Codex, Copilot

Claude Code, Codex, Copilot - And any other agent that reads the open Agent Skills format. The frbit CLI installs the skill and connects the MCP server in one command; in Claude Code, the fortrabbit plugin does the same.

#
Is an MCP connection required?
No

No - The skill works over SSH and rsync on its own. Adding the MCP server lets the agent list apps, create environments and read deployment logs without a shell β€” the two halves compose rather than compete.

#
What does it do?
The everyday operations

The everyday operations - Find the environment of the current repo, deploy and follow the deployment, pull or push a database, sync uploads and files, run artisan, craft console or Composer over SSH, and trace a 500 error to its cause.

#
What does it need locally?
git, ssh, rsync

git, ssh, rsync - A MySQL client too, for database work. On Windows, rsync needs WSL; SSH works natively on Windows 10 and later.

#