MCP, CLI and API are here

# Fuzzy as a feature

I don't know about you. I am excited and also very concerned about LLMs. It for sure has profound impact on our guild. Let's focus on the good parts now. I like how I can use vague, fuzzy input with only implicit instructions, still getting to concrete results. Now, we are releasing better interfaces for your agents to connect to our platform and work with fortrabbit domain knowledge.

# Simplistic demo

> I want this deployed to fortrabbit!

This is a Craft CMS project. I can create a trial app for you on fortrabbit.
Do you want Git deployment?

> Yes.

You have a GitHub repo connected, and your fortrabbit account is connected to
GitHub as well. Which region should the app live in, EU or US?

> US!

…

The moving parts are:

# MCP: agents - NEW

The Model Context Protocol is a standard way for an agent to ask a service what it can do. Instead of teaching an agent which endpoints exist, the agent asks and gets a described list of tools back. The fortrabbit MCP server sits at:

• https://mcp.fortrabbit.com/mcp

Authorization happens in the browser. An agent can read/edit apps and environments and the reference data it needs to create one, like software presets, PHP versions, components, connected repos and branches.

• MCP setup - for Codex, Cursor & VS Code
• MCP docs - more details

# CLI: agents, terminal, pipelines - NEW

frbit is a single binary written in Go, no runtime dependency. Everything it does is an API call under the hood. It can also be steered by an agent (They love it). Not everything is agentic. A deployment pipeline may require exit codes and flags. That is a use case for the CLI, a boring, deterministic, good old automation.

• CLI docs - install and commands
• github.com/fortrabbit/frbit-cli↗ - source

# API: base - NEW

The public API offer even more automation options. REST over https://api.fortrabbit.com/v1, authenticated with a personal API token created in the dashboard. An API token acts as the person who created it. Apps, environments, deployments, domains, teams, people, payment methods.

• api.fortrabbit.com/v1/docs↗ - endpoint reference
• API docs - more details

# Skills: glue - UPDATED

We shipped the fortrabbit agent skills as an early preview in April. Back then everything went through SSH and Git. Now with API and CLI the skills got a lot smarter.

There are two skills now. fortrabbit covers the workflows: deployment, SSH, database and content sync, and MCP-based discovery and provisioning. fortrabbit-api-access covers the credentials — connecting an agent to the MCP server, or issuing an API token where a browser flow does not fit, like in CI.

• Agent skills docs
• github.com/fortrabbit/agent-skills↗

# Bring your own agent

fortrabbit is BYO agent, at least until we see real benefit/need to integrate our own. Like with other aspects of fortrabbit, will we not design it as a vendor lock-in. Our aim is to keep AI features optional to support the old sacred craft of manual web development.

Build great things!

# Still in BETA

Mind that the whole platform is in BETA. We are dropping a lot of features at once. All of them are tested, none of them are battle proven, and there is no test like production. There will be bugs. Please report issues. We aim to respond quickly. Those are sharp tools. Use them responsibly. Stay safe kids.

# Outlook

This automation suite was a bit of a detour from our main roadmap to bring feature parity and more hardening for the new platform to finally make it generally available (by removing the BETA flag). We will now turn back to that. Up next, small improvements and bug fixes, but also still missing features. I am looking forward to see dashboard metrics getting released soon.