Developer · Local MCP server
Buildtree
Upload Android and iOS builds to buildtree and get install links, QR codes and tester feedback.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.engineerdeep/buildtree- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- engineerdeep (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/engineerdeep) · how
- Website
- buildtree.sh/docs/mcp
- Repository
- github.com/engineerdeep/buildtree-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @buildtree/mcp | 0.1.2 | stdio |
How to connect Buildtree
Buildtree runs locally from a Node.js package published to the npm registry: @buildtree/mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @buildtree/mcp@0.1.2. It reads these environment variables: BUILDTREE_TOKEN (secret) and BUILDTREE_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"buildtree": {
"command": "npx",
"args": [
"-y",
"@buildtree/mcp@0.1.2"
],
"env": {
"BUILDTREE_TOKEN": "<secret>",
"BUILDTREE_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| BuildStart a NorthernGo cloud build from Cursor, Claude or Codex. EU database included. | Remote · HTTPLive check: sign-in required |
| BuilderforceRun tickets, boards, OKRs and cloud coding agents in your Builderforce workspace. | Remote · HTTPLive check: sign-in required |
| Buildkite MCP ServerMCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors. | Local · stdio |
| BuildPulseBuildPulse CI test analytics for AI agents - flaky tests, CI failures, flakiness, and code coverage. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Buildutilities MCPDeterministic dev utilities: UUIDs, hashes, encoding, JWT, cron, regex. No network, no API key. | Local · stdio |
| Bulk Sender Lint21 dated checks over SPF, DKIM, DMARC, RFC 8058 one-click unsubscribe and TLS, in VS Code and in the. | Local · stdio |
| BulwarkAI agent governance: content scanning, audit logs, policy evaluation, session management. | Local · stdio |
| Bumblebeereceipt MCPA paid remote MCP for developer endpoint scanner MCP, built to return verdicts, receipts, usage logs. | Remote · HTTPLive check: ✗ no handshake |