MCP server

Anything speaking MCP - Claude Code, Codex, Cursor and VS Code have a documented setup command each. Any other MCP client works against the same endpoint. A client without OAuth support authenticates with a personal API token instead.

Three things - Most tools read. Three write: creating an app, creating an environment, and updating environment variables. Restarts, deletions and standalone deployments are not exposed — a REST endpoint existing does not make it available to agents.

Never - A connection carries the authorization of the person who approved it and sees exactly what that person sees in the dashboard. The access token expires after one hour and the refresh token after 30 days, both bound to that one agent.

From either side - Clearing the authentication in the agent drops the access token and the refresh token together, so it cannot quietly renew. Disconnecting on the account side ends every connection that agent holds — the route to take when the machine running it is out of reach.

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 whatever an agent reads lands in the context of the connected client. Worth a thought before pointing one at a production environment.