# buildtree [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/engineerdeep/buildtree-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/buildtree-2

## Description
Upload Android and iOS builds to buildtree and get install links, QR codes and tester feedback.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "buildtree": {
    "command": "npx",
    "args": ["-y","@buildtree/mcp"],
    "env": {
      "BUILDTREE_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `BUILDTREE_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What buildtree does

The buildtree MCP server helps coding agents prepare mobile apps for testing through buildtree. It supports Expo, React Native, Flutter, native Android, and native iOS projects. An agent can identify the project type, suggest build commands, create a buildtree configuration file, run the build, and upload the resulting `.apk` or `.ipa` file.

After an upload, the server returns an install link and QR code that can be shared with testers. It can also list existing builds, retrieve install links for a selected build, and read tester feedback that includes screenshots. This makes it relevant to the Developer Tools category for workflows where an agent handles both build distribution and feedback collection.

## How it works

The buildtree MCP server exposes tools, resources, and a setup prompt through MCP. The `setup` prompt and the `buildtree://guide` resource describe the general workflow. Framework-specific resources provide build recipes for Expo, React Native, Flutter, Android, and iOS.

Project and account operations are handled through tools such as `buildtree_list_projects`, `buildtree_create_project`, and `buildtree_whoami`. `buildtree_detect_project` examines the app and suggests an appropriate build approach. `buildtree_build` runs that build with progress updates, while `buildtree_upload` sends the output to buildtree.

Authentication can be completed through a browser. The login is shared with the buildtree CLI, so signing in through one can provide access to the other. For CI use, an API token from the buildtree dashboard can be supplied through `BUILDTREE_TOKEN`; tokens are not shown in tool output.

## Setup and configuration

The local package requires Node.js 20 or later. A standard stdio installation runs the package with `npx -y @buildtree/mcp`. Claude Code, Codex CLI, Gemini CLI, Cursor, Windsurf, and Claude Desktop can use this command through their MCP configuration. Claude Desktop can alternatively install the `.mcpb` file from the latest GitHub release.

A remote read-and-share server is available at `https://buildtree.sh/api/mcp` and uses OAuth 2.1. This option does not require local installation for sharing links or reading feedback. The local server is intended for agents that also need to build and upload an app. Claude Code can add either transport, and ChatGPT can connect to the remote URL as a custom MCP server.

## Tools and capabilities

The buildtree MCP server includes tools for:

- Checking the account, organization, and plan.
- Starting browser login and checking login status.
- Listing and creating one buildtree project per app.
- Detecting supported mobile frameworks.
- Writing `buildtree.config.json`.
- Running builds with progress updates.
- Uploading builds and returning install links and QR codes.
- Listing builds and retrieving links for an existing build.
- Reading tester feedback and screenshots.

## Limitations and notes

The material documents Android and iOS workflows and the five supported project types listed above. It does not describe other platforms or project frameworks. Interactive authentication opens a browser for approval, while CI requires an API token. The remote endpoint covers sharing and feedback access; building and uploading are described for the local server.

The buildtree MCP server is MIT licensed. Its documented MCP resources and prompt provide workflow guidance, but the actual app build still depends on the selected framework and its build commands.

_Full upstream README: https://allmcps.com/mcp/buildtree-2/readme_