fortrabbit

fortrabbit MCP server

Connect a coding agent to drive the hosting platform.

About the MCP server → MCP server documentation →

claude mcp add --scope user --transport http fortrabbit https://mcp.fortrabbit.com/mcp

Authorization runs on the first connection, not on add. Run /mcp and pick fortrabbit, then authenticate.

Frequently asked

What is the fortrabbit MCP server endpoint?

https://mcp.fortrabbit.com/mcp

https://mcp.fortrabbit.com/mcp - The server speaks streamable HTTP at https://mcp.fortrabbit.com/mcp. Point any MCP client at that URL; the setup commands above only write it into the client configuration.

#

What can a connected agent do?

Mostly read

Mostly read - It lists apps, environments, deployments, domains, teams and payment methods, and it reads deployment logs. Three tools write: create an app, create an environment, update environment variables. Restarts and deletions are not exposed.

#

Is an API token needed to connect an agent?

Not for OAuth clients

Not for OAuth clients - Claude Code, Codex, Cursor and VS Code authorize in a browser on the first connection, so no credential is stored in a config file. A client without OAuth support falls back to a personal API token issued in the dashboard.

#

How is an agent connection revoked?

From either side

From either side - Clearing the authentication in the agent drops the access token and the refresh token together, so it cannot quietly renew. Disconnecting under AI agents in the dashboard ends every connection that agent holds.

#

Is it ready for a production environment?

It is in testing

It is in testing - The MCP server is in testing and the platform around it is in beta. Reading environment variables returns the values fortrabbit injects, database credentials among them, and those land in the context of the connected client.

#

Is MCP the only way to automate the platform?

No

No - The same operations are available over the public REST API and the frbit CLI.

#