F
licenseNot graded
qualityD
maintenanceAuto-generated MCP server that enables interaction with the Firebase App Distribution API, allowing users to manage distribution of pre-release app builds to testers through natural language commands.
-
buildtree
by engineerdeep
Related Servers
Alternatives to buildtree
Related Servers
@appdropper/mcpofficial
AlicenseAqualityCmaintenanceEnables coding agents to upload local .apk or .ipa builds and receive tester install links without leaving the editor.66 npmMIT- AlicenseAqualityCmaintenanceBuild, sign, and publish iOS and Android apps through AI agents. Integrates Codemagic CI/CD, App Store Connect, and Google Play in one server.6324 npm1MIT
@betadrop/mcpofficial
AlicenseAqualityAmaintenanceEnables AI coding assistants to distribute iOS and Android builds to BetaDrop testers, manage share links, track releases, and manage API tokens entirely through natural language prompts.1160 npmMIT- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.177 npm8MIT
appcircle-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to interact with Appcircle mobile CI/CD platform for build management, signing identities, testing distribution, and reporting.25MIT- AlicenseCqualityBmaintenanceEnables AI-assisted mobile development workflows with guarded build, Appium testing, security scanning, verification, and evidence-based fix-retest loops on Android and iOS.8211MIT
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation4/5
Each tool has a distinguishable purpose: auth flow (whoami/login/login_status), project management, config generation, build, upload, and feedback are distinct steps. Minor potential confusion between list_builds and get_install_links, and among the three auth tools, but descriptions clarify the pipeline clearly.
Naming Consistency5/5
Every tool uses the buildtree_ prefix followed by a consistent snake_case verb_noun pattern (list_projects, create_project, detect_project, write_config, list_builds, get_install_links, list_feedback). The few noun-only variants (whoami, build, upload) are still clear and idiomatic.
Tool Count5/5
12 tools is well within the ideal 3-15 range and each tool maps to a concrete step of the build/upload/feedback workflow. No redundant or filler tools are present.
Completeness4/5
The surface covers the full lifecycle: authenticate, manage projects, detect/write config, build, upload, and read install links and feedback. Minor gaps exist (no project update/delete or config re-edit beyond overwrite, no feedback resolution), but core workflows have no dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues