@betadrop/mcp
OfficialBetaDrop MCP lets an AI assistant publish iOS/Android builds, manage build history, and handle API tokens through natural prompts.
Authenticate with a BetaDrop API token (
betadrop_login), revoke it (betadrop_logout), or check account details (betadrop_whoami).Publish
.ipaor.apkbuilds (betadrop_publish), overriding app name, version, build number, bundle ID, and release notes, and setting expiry by time, downloads, devices, or combined limits.Retrieve the install link for large uploads that outrun the 90-second publish window (
betadrop_upload_status).List recent builds (
betadrop_list_builds) filtered by platform (ios/android) and status (active,expired,disabled,deprecated,latest) with pagination.List expired builds directly (
betadrop_list_expired_builds) with expiry reasons.Manage API tokens: list active tokens (
betadrop_token_list), create scoped tokens with abilities (publish,read,*) and optional 1–365 day expiry (betadrop_token_create), and revoke a token by ID (betadrop_token_delete).Access an offline tool reference (
betadrop_help).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@betadrop/mcp Upload the newest Android APK to BetaDrop and share the link with testers."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@betadrop/mcp
"Publish this build and send me the install link." Say that to your AI assistant and a tester can be installing the app thirty seconds later.
BetaDrop puts an iOS .ipa or Android .apk behind an over-the-air install
link: testers open the link on their phone and install straight from the browser — no TestFlight
review wait, no Play track, no tester accounts. If you have used Diawi or Firebase App Distribution,
it does the same job.
BetaDrop MCP moves that step to the other side of your AI assistant. Claude, Cursor, Copilot, Windsurf, Zed and Antigravity can publish builds, check they will install, manage standing links, devices and webhooks, and read tester feedback through ordinary prompts — no browser tab, no CLI, no leaving the editor.
claude mcp add betadrop -s user -- npx -y @betadrop/mcp23 tools. One npx command. No build step. Your assistant already knows how to use them — you never type a tool name.
⚡ Quick Start (3 Steps)
Step 1 — Get a BetaDrop API Token
Sign up or log in at betadrop.app
Go to Settings → Developer
Under API tokens, click Create token, give it a name (e.g.
"My IDE"), and copy the token
(It starts withbd_live_...— save it somewhere safe, it's shown only once!)
Step 2 — Add the MCP Server to Your Editor
🤖 AI-Native Installation (Easiest) Since you are already using an AI assistant (like Cursor Composer, Claude, Copilot, or Antigravity), you don't need to edit configuration files manually! Just paste one of the following prompts directly into your AI chat:
Cursor:
"Add the @betadrop/mcp server to my global Cursor mcp.json config"Antigravity:
"Add the @betadrop/mcp server to my Antigravity mcp_config.json"VS Code (Copilot):
"Add the @betadrop/mcp server to my workspace .vscode/mcp.json"Claude Desktop:
"Add the @betadrop/mcp server to my Claude Desktop config"
The AI will automatically locate, create, or update the configuration file for you. Once it is done, simply refresh/restart your editor.
Otherwise, pick your editor below to configure it manually.
Run one command in your terminal:
claude mcp add betadrop -s user -- npx -y @betadrop/mcpThis installs BetaDrop globally across all your Claude Code projects.
For a single project only, drop the-s userflag.
Verify it worked:
claude mcp listStart a new Claude Code session and type /mcp to confirm the connection.
Open your config file:
OS | Path |
macOS |
|
Windows |
|
Add this inside the file:
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Restart Claude Desktop. BetaDrop tools will appear in the 🔧 tools panel.
Create .cursor/mcp.json in your project root:
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Or for global access, create/edit ~/.cursor/mcp.json with the same content.
Go to Settings → MCP and click Refresh to pick up the new server.
Create .vscode/mcp.json in your project root:
{
"servers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Or add it globally:
OS | Path |
macOS |
|
Windows |
|
Linux |
|
Use Copilot in Agent mode to access BetaDrop tools.
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Add to your Zed settings file:
OS | Path |
macOS |
|
Linux |
|
{
"context_servers": {
"betadrop": {
"command": {
"path": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}
}Open MCP settings from Settings → MCP Servers or edit the config file directly:
OS | Path |
macOS |
|
Windows |
|
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Restart Antigravity to pick up the new server.
Step 3 — First-Time Setup
After adding the MCP server, authenticate with your BetaDrop API token. Open your AI assistant and type:
"Log me in to BetaDrop with token bd_live_xxxxxxxx"
Your credentials are saved to $XDG_CONFIG_HOME/betadrop/config.json when that variable is set, otherwise ~/.betadrop/config.json, with 0600 permissions (owner-read only). On logout, the token is revoked on the server and the config file is removed.
✅ You're all set! Now try any of these prompts 👇
Related MCP server: App Store Connect MCP Server
🚀 Try These Prompts
You don't need to memorize any tool names — just talk to your AI assistant naturally:
📦 Publishing Builds
Prompt | What Happens |
| Uploads the IPA and returns an install link |
| Publishes with release notes visible to testers |
| Sets a time-based expiry on the build |
| Returns a shareable OTA install URL |
📋 Build History
Prompt | What Happens |
| Lists your latest builds across both platforms |
| Filters to iOS only |
| Lists builds that have hit their expiry limit |
| Expired builds filtered by platform |
| Retrieves the shareable URL |
🔑 Token Management
Prompt | What Happens |
| Lists all active tokens with abilities and expiry |
| Creates a new token scoped for CI |
| Creates a token whose abilities are recorded as |
| Auto-expiring token for temporary access |
| Permanently revokes a token |
✅ Release Checks, Links and Devices
Prompt | What Happens |
|
|
| Publishes and points the standing link testers already have at it |
| Reads tester feedback |
| Returns the tab-separated devices file |
| Creates a webhook formatted for Slack |
👤 Account
Prompt | What Happens |
| Shows your email, token details, and API URL |
| Revokes the token server-side and clears local config |
🔁 Chained, in one turn
Because these are tools and not a chat bot, your assistant can string them together:
"Build the release APK, publish it to BetaDrop with the last commit message as the notes, and give me the install link."
The build runs in your terminal, betadrop_publish uploads the artifact, and the link comes back
in the same reply.
📖 All Available Tools
Twenty-three tools across eight areas. You never call these by name — the assistant picks them.
Authentication
Tool | What It Does |
| Save and validate your API token |
| Revoke the token on the server and clear local credentials |
| Show your account email, token name, and expiry |
Publishing Builds
Tool | What It Does |
| Upload an |
| Get the result (install link) of the most recent |
betadrop_publish parameters:
Parameter | Type | Required | Description |
| string | ✅ | Absolute path to the |
| string | Override the app display name | |
| string | Override the version string (e.g. | |
| string | Override the build number | |
| string | Override the bundle / package ID | |
| string | Release notes shown on the install page | |
| string |
| |
| number | Expire after N days (use with | |
| number | Expire after N downloads (use with | |
| number | Expire after N unique devices (use with | |
| string | Slug of a standing link to point at this build once it is live (must already be claimed on the account) |
Expiry is capped by your plan.
none— a permanent link — is a paid-plan feature; on a plan without it the build is stored as a dated one instead of being rejected.expiryTimeDaysis clamped to your plan's maximum build retention on every plan. When either happens the server returns aretentionClampobject (requestedDays,appliedDays,maxDays,permanentDenied,message) and the tool result appends a ⚠️ line explaining what was applied. Note it is reported only when the plan actually shortened something you asked for: send noexpiryTimeDaysand it stays null even if your account default was clamped down. Current per-plan day ceilings live insrc/lib/limits.jsonrather than being restated here.
How uploads work: The file is validated locally (ZIP magic bytes check) and uploaded, with progress notifications streamed to your AI client in 5% increments. The install link comes back in the tool result. Builds that take longer than 90 seconds keep uploading in the background so the tool call does not time out — the assistant then calls
betadrop_upload_statusto fetch the link. A status file at~/.betadrop/upload_status.jsontracks the upload in real time.
Build History
Tool | What It Does |
| List recent builds, with optional filters |
| List only expired builds (convenience shortcut) |
betadrop_list_builds parameters:
Parameter | Type | Required | Description |
| string |
| |
| string |
| |
| number | Page number (default: | |
| number | Results per page (default: |
betadrop_list_expired_builds parameters:
Parameter | Type | Required | Description |
| string |
| |
| number | Page number (default: | |
| number | Results per page (default: |
Each result includes the build name, version, platform, file size, status, dates, and a shareable install link.
Token Management
Tool | What It Does |
| List all your active (non-revoked) API tokens |
| Create a new scoped token (plaintext shown only once!) |
| Permanently revoke a token by ID |
betadrop_token_create parameters:
Parameter | Type | Required | Description |
| string | ✅ | Label for the token (max 100 chars) |
| string[] |
| |
| number | Token lifetime in days (1–365). Omit for no expiry |
Abilities are enforced on every endpoint: a
readtoken can list builds, read feedback and runbetadrop_inspect, but cannot publish, delete, or change links, devices or webhooks.
⚠️ The plaintext token is shown exactly once at creation. Copy it immediately!
Release Checks
Tool | What It Does |
| Will an |
Standing Links
Tool | What It Does |
| Standing links, the build each serves, and follower counts |
| Point one at an already-uploaded build; followers are emailed |
betadrop_publish also accepts standingLink to point one at the new build as it goes live.
Builds, Feedback and Devices
Tool | What It Does |
| Delete a build; its install link stops working |
| Feedback testers left on a build |
| Registered iOS devices (UDIDs) |
| The devices file Apple's portal and fastlane |
| A link a tester opens on their iPhone to register it |
Webhooks
Tool | What It Does |
| Webhooks on the account |
| Send events to a URL, Slack or Discord (detected from the URL) |
| Deliver a test event now and report the answer |
| Remove a webhook |
Quick Help
Tool | What It Does |
| Show a full offline reference of all tools and example prompts |
⚙️ Configuration
Set these environment variables to override the defaults:
Variable | Default | Description |
|
| API server URL (for self-hosted) |
|
| Frontend URL for install links |
| (none) | Token for CI — skips the local config file |
To set them for the MCP server, add an env block alongside command and args in the editor
config from Step 2:
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"],
"env": { "BETADROP_TOKEN": "bd_live_xxx" }
}
}
}With BETADROP_TOKEN set there is no need to log in — the server uses it directly:
BETADROP_TOKEN=bd_live_xxx betadrop-mcp❓ Troubleshooting
"Tool not found" or no BetaDrop tools showing up?
Make sure Node.js 18+ is installed:
node --versionRestart your editor after adding the MCP config
In Claude Code, run
/mcpto check the server statusIn Cursor, go to Settings → MCP and click Refresh
"You are not logged in"?
Ask your AI:
"Log me in to BetaDrop with token bd_live_..."Or set the
BETADROP_TOKENenv variable in your MCP config — see Configuration
Upload seems stuck?
Builds that take longer than 90 seconds keep uploading in the background so the tool call does not time out
Ask your assistant to check the upload status (it will call
betadrop_upload_status) — that returns the install link once the upload landsYou can also watch
~/.betadrop/upload_status.jsondirectly
Token expired or revoked?
Create a new token at betadrop.app → Settings → Developer → API tokens
Log in again with the new token
The iOS build downloads on the phone but will not open?
An ad-hoc
.ipaonly installs on devices that were in the provisioning profile when it was signed — publishing it does not change that. Send the tester the UDID checker, add the device in the Apple Developer portal, and re-sign.
Also from BetaDrop
The same publish step, on the other two surfaces — one account, one set of API tokens:
| |
Publish from a GitHub Actions workflow. The install link lands on the run summary and, optionally, in a pull-request comment that updates itself on every push. |
📚 Links
BetaDrop — the build distribution platform
Model Context Protocol — the open standard powering this integration
Requirements
Node.js 18+
A BetaDrop account — the free tier needs no card. Retention and file-size ceilings by plan are on the pricing page.
One of the supported AI editors (Claude, Cursor, VS Code, Windsurf, Zed, Antigravity)
Contributing
Issues and pull requests: https://github.com/betadrop-app/betadrop-mcp. If this saved you a trip to the browser, a ⭐ helps other mobile teams find it.
License
MIT
Available Tools
11 toolsbetadrop_helpA
Get a quick reference of all available BetaDrop MCP tools, their inputs, and example prompts.
Inputs: no named parameters.
betadrop_list_buildsB
List recent builds published to BetaDrop, optionally filtered by platform and status.
Inputs: page, status, perPage, platform.
betadrop_list_expired_buildsA
List all expired builds on BetaDrop. Shortcut for listing builds with status 'expired'. Shows expiry reason and details.
Inputs: page, perPage, platform.
betadrop_loginA
Configure API authentication with a BetaDrop token. Validates the token against the server and saves credentials to the shared CLI config.
Inputs: token (required), apiUrl.
betadrop_logoutA
Revoke the active token on the server and clear local credentials.
Inputs: no named parameters.
betadrop_publishB
Publish an iOS (.ipa) or Android (.apk) build to BetaDrop.
Inputs: filePath (required), name, notes, version, +6 more.
betadrop_token_createA
Create a new CLI token. The plaintext token is shown exactly once — copy it immediately.
Inputs: name (required), abilities, expiresInDays.
betadrop_token_deleteA
Revoke a CLI token by its ID.
Inputs: tokenId (required).
betadrop_token_listA
List all active CLI tokens for the current account.
Inputs: no named parameters.
betadrop_upload_statusA
Get the result of the most recent betadrop_publish upload, including the install link. Call this only when betadrop_publish reported the upload was still running.
Inputs: no named parameters.
betadrop_whoamiA
Check authentication status and show the active account and BetaDrop server details.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools map to a distinct action or resource (auth, publish, builds, tokens), and descriptions clarify intended use. However, betadrop_list_builds and betadrop_list_expired_builds overlap heavily, since the latter is just a filtered shortcut for the former, creating some selection ambiguity.
All tools share a uniform betadrop_ prefix and lowercase snake_case, which is helpful. But naming style is mixed: build commands use verb-first (list_builds) while token commands use noun-first (token_list, token_create), and whoami/login/logout are not verb_noun. Overall readable and mostly predictable.
Eleven tools is well-scoped for a BetaDrop-focused server; each tool covers a meaningful part of auth, publishing, build listing, and token management. No obvious bloat or redundancy.
Auth lifecycle, publishing/upload status, build listing, expired listing, and token management cover the core workflows an agent would need for BetaDrop. Minor gaps exist, such as no per-build detail/delete or expanded server info, but they are not dead ends.
Maintenance
Related MCP Connectors
Share iOS and Android test builds: upload, install links, testers, store readiness and releases.
Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access TestFlight beta tester feedback, including screenshots, crash logs, and text comments from App Store Connect. It works across any platform without requiring Xcode, using official API keys and optional browser automation for full text feedback.8MIT
- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.15 npm8MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.2014 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnects AI coding clients like OpenCode, Codex, and Claude Code to Xcode and Apple development tools, enabling builds, tests, simulator and device management, profiling, asset handling, and more through natural language.129 npm1MIT