MCP connector
Give Claude your Buildfyio workspace as tools — hosted, no install.
Add it to Claude
Buildfyio runs a hosted MCP server, so there is nothing to install. In Claude, add a custom connector with this URL:
https://mcp.buildfyio.com/mcp
Claude opens a Buildfyio sign-in, you pick the workspace to grant and approve. It never asks you for a token.
What it can do
| Tool | Needs | What it does |
|---|---|---|
| list_projects | read | List the projects in the workspace |
| get_deployment_status | read | Status and URL of a deployment |
| get_logs | read | Read the archived build, deploy or runtime log |
| get_build_failure | read | Why a build failed, with a suggested fix |
| deploy | deploy | Trigger a deployment |
| rollback | deploy | Roll back to a previous deployment |
| create_project | write | Create a project from a Git repo |
| set_env_var | write | Create or overwrite an environment variable |
Permissions
You choose the scopes when you approve. A tool that needs more than you granted is refused with a message saying so — it does not fail silently or quietly do less.
read— see projects, deployments, logs and build failures.deploy— trigger deployments and roll back.write— create projects and change environment variables.
Claude (MCP connector). Revoke it under Settings → API tokens; the connector stops working immediately.Running it locally instead
If you would rather not use the hosted server — an air-gapped setup, or a self-hosted Buildfyio — the same tools ship as a stdio server you run yourself:
npm i -g @fyio/buildfyio-mcp buildfy mcp install claude-code # or: claude-desktop | cursor | windsurf
That path mints its own scoped token and writes the client config for you. Point it at another API with BUILDFYIO_API_URL.
For client authors
The server speaks JSON-RPC 2.0 over HTTP and authenticates with OAuth 2.1 (PKCE required, dynamic client registration supported). Discovery follows the specs, so a compliant client needs nothing but the URL above:
GET https://mcp.buildfyio.com/.well-known/oauth-protected-resource GET https://api.buildfyio.com/.well-known/oauth-authorization-server
An unauthenticated call returns 401 with a WWW-Authenticateheader pointing at the resource metadata.