Buildtree

io.github.engineerdeepPublished by GitHub account engineerdeepv0.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Lets an AI coding agent set up buildtree, build and upload Android or iOS apps, and return install links, QR codes and tester feedback.

What you can do
Buildtree's local MCP server wraps the buildtree mobile build-sharing workflow. Tools cover account lookup, browser login, project listing and creation, framework detection for Expo, React Native, Flutter and native apps, writing buildtree.config.json, running builds with progress updates, uploading the resulting .apk or .ipa, and retrieving install links, QR codes and tester feedback with screenshots. It also exposes guide and framework recipe resources plus a setup prompt.
When to use it
Use it when a coding agent should take a mobile app from source to a shareable test build: detecting the framework, configuring the project, running the build, uploading it, and handing back an install link or QR code for testers. It also fits reading tester feedback and screenshots back into the agent.
Requirements
Runs locally over stdio via npx @buildtree/mcp, so Node 20 or later is required. A buildtree account is needed; sign-in happens through a browser page the first time, or by setting BUILDTREE_TOKEN from the buildtree dashboard for CI. BUILDTREE_API_URL optionally overrides the API origin, which defaults to Desktop only.
Before you install
The server can run builds and upload app binaries to buildtree's service, so build artifacts leave the machine. BUILDTREE_TOKEN is a credential and should be treated as a secret; the README states tokens never appear in tool output. Login is shared with the buildtree CLI, so approving it grants the agent the same account access. Builds may consume buildtree plan quota.

Installation

In SourceWeft

  1. Open Buildtree in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

buildtree MCP server

[npm] [buildtree MCP server on Glama]

MCP server for buildtree, the fastest way to share Android and iOS builds with testers. Let your AI coding agent set up buildtree for your app, run the build, upload the .apk or .ipa, and hand you an install link and QR code to share. It can also read the feedback and screenshots testers send back.

Works with Expo, React Native, Flutter, and native Android and iOS apps, in Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor and Windsurf.

"Set up buildtree for this app and give me a QR code for an Android build."

Remote server and ChatGPT plugin

You do not need to install anything to share links and read feedback: buildtree runs this server's read-and-share half at https://buildtree.sh/api/mcp (OAuth 2.1).

Claude Code, remote server (sign in once through the browser):

bash
claude mcp add --transport http --scope user buildtree https://buildtree.sh/api/mcp

Then run /mcp, pick buildtree, choose Authenticate, and approve in the browser.

Claude Code, the plugin (skills plus the local server, which can also build and upload). Inside Claude Code:

/plugin marketplace add engineerdeep/buildtree-mcp/plugin install buildtree@buildtree

Codex: codex plugin marketplace add engineerdeep/buildtree-mcp, then install buildtree from the Plugins directory.

ChatGPT: Plugins, the plus button, Add custom MCP server, URL https://buildtree.sh/api/mcp.

Step-by-step with what to expect at each screen: https://buildtree.sh/docs/chatgpt. The local server below is for coding agents that also build and upload.

Install

Claude Code

bash
claude mcp add --transport stdio buildtree -- npx -y @buildtree/mcp

Claude Desktop: download buildtree-mcp-<version>.mcpb from the latest release and double-click it. Or add the JSON below to claude_desktop_config.json.

Codex CLI (~/.codex/config.toml)

toml
[mcp_servers.buildtree]command = "npx"args = ["-y", "@buildtree/mcp"]tool_timeout_sec = 1800

Gemini CLI, Cursor, Windsurf, Claude Desktop (JSON)

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

Requires Node 20 or later.

Tools

ToolWhat it does
buildtree_whoamiAccount, organization and plan
buildtree_login, buildtree_login_statusBrowser login, shared with the buildtree CLI
buildtree_list_projects, buildtree_create_projectOne project per app
buildtree_detect_projectDetects Expo, React Native, Flutter or native and suggests build commands
buildtree_write_configWrites buildtree.config.json
buildtree_buildRuns the build with progress updates
buildtree_uploadUploads the build; returns install links and a QR code image
buildtree_list_builds, buildtree_get_install_linksBrowse builds, get links and QR for any build
buildtree_list_feedbackTester feedback with screenshots

Resources: buildtree://guide (the workflow) and buildtree://frameworks/{expo|react-native|flutter|android|ios} (build recipes). Prompt: setup.

Sign in

The first time, your agent opens a browser page where you approve the connection. The login is stored where the buildtree CLI keeps its own, so either can sign in for both. In CI, set BUILDTREE_TOKEN to an API token from the buildtree dashboard. Tokens never appear in tool output.

Links

MIT licensed.

Source: README.md at commit 7edc363

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.1.2LatestSep 29, 2026
  2. v0.1.1Sep 27, 2026
  3. v0.1.0Sep 27, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts