buildtree in ChatGPT

buildtree runs a remote MCP server at https://buildtree.sh/api/mcp. Connect it to ChatGPT, Claude, Cursor or any client that speaks MCP over HTTPS, sign in once, and ask things like "give me the QR code for the latest Android build on dev" or "what did testers say about the payments branch build". In ChatGPT the install links come back as a card with a scannable QR code.

This is the read-and-share half of buildtree. Uploading a build still happens from the CLI, the dashboard, or a coding agent with the local MCP server, which also runs your build.

Add it to ChatGPT

Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
Name it buildtree and enter the server URL https://buildtree.sh/api/mcp. Leave authentication on OAuth.
Select Create as a plugin, then install it from your personal plugins.
Start a new chat. The first request opens a buildtree sign-in page in your browser: enter your email, click the magic link, and confirm the connection.
Type @buildtree or just ask: "share the latest iOS build on staging with the testers".

A listing in the ChatGPT plugin directory is in review; once it is live, installing from the directory replaces steps 1 to 3.

Add it to Claude

Claude Code

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

Start claude in any folder, run /mcp, choose buildtree, then Authenticate. Your browser opens the buildtree sign-in page saying that an app wants to connect.
Enter your email and open the magic link. You land on a "Connect ... to buildtree" screen listing what the connection can do. Press Allow. The browser hands control back to Claude Code, which now shows the server as connected.
Ask: "Which projects do I have on buildtree?" then "Give me the install link and QR code for the latest Android build on dev."

Tokens refresh on their own. If a call ever comes back unauthorized, run /mcp and authenticate again. To remove the server: claude mcp remove buildtree.

For CI or scripts, pass an API token from the dashboard's API Tokens page instead of signing in:

claude mcp add --transport http buildtree https://buildtree.sh/api/mcp --header "Authorization: Bearer $BUILDTREE_TOKEN"

Claude Desktop, Cursor, Windsurf: add the remote server in the app's connector or MCP settings with the URL https://buildtree.sh/api/mcp. Clients that only support local servers can use the stdio server instead.

What you can ask

Tool	What it does
`buildtree_whoami`	Which account and plan is connected.
`buildtree_list_projects`	Your projects (one per app).
`buildtree_create_project`	Create a project when you ask for one.
`buildtree_list_builds`	Builds in a project, filtered by environment, branch or platform.
`buildtree_get_install_links`	Install links and a QR card for a build, or for the latest build of an environment or branch.
`buildtree_list_feedback`	What testers reported, with screenshot links.
`buildtree_set_feedback_status`	Mark feedback resolved, or reopen it.

Example prompts:

"Give me the install link and QR code for the latest Android build on dev."
"Share the iOS build from the feature/payments branch with the testers."
"What did testers report on the last build? Group the bugs."
"Which builds are on staging right now?"
"Mark the login bug feedback as resolved."

Codex and Claude Code plugin

The same skills ship as a plugin for Codex and Claude Code, with the local server so the agent can also build and upload. Add the marketplace, then install buildtree from the Plugins directory in the ChatGPT desktop app (or /plugins in the Codex CLI):

codex plugin marketplace add engineerdeep/buildtree-mcp

In Claude Code:

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

The plugin's skills, share-build and triage-feedback, teach the agent the buildtree workflow; the source is at github.com/engineerdeep/buildtree-mcp.

First use with the plugin: open a session in your app's folder and say "log in to buildtree". The local server opens a browser page where you approve the connection, and the token is stored where the buildtree CLI keeps its own, so one login serves both. Then try "share the latest build on dev with the testers" or "set up buildtree for this app and give me a QR code for an Android build". The local server needs Node 20 or later.

Security notes

Sign-in uses OAuth 2.1 with PKCE. buildtree never shares your password (there is none) and never shows API tokens in a chat.
Tester feedback text is written by other people. The tools label it as untrusted input so the assistant summarizes it instead of acting on it.
Each tool declares whether it reads or writes, so ChatGPT asks before anything that changes state.

Last updated October 11, 2026

PreviousGitHub Actions Next MCP server for coding agents