BetaDrop

io.github.betadrop-appPublished by GitHub account betadrop-appv0.2.5Updated Oct 24, 2026

Publish iOS and Android builds to testers and manage share links from an AI coding agent.

The publisher's own server: drop.media

VerifiedSTDIODesktop onlyProductivity & Workflow Files & Storage Developer Tools

Server details

Identifier: io.github.betadrop-app/betadrop-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account betadrop-app for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.betadrop-app%2Fbetadrop-mcp.svg)](https://sourceweft.com/mcp/io.github.betadrop-app%2Fbetadrop-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

BetaDrop publishes iOS and Android test builds and manages install links, devices, webhooks and tester feedback from an AI coding assistant.

What you can do: Publish and check builds: upload an .ipa or .apk, get an over-the-air install link, set expiry, and inspect signing before publishing
Review build history: list recent or expired builds by platform and status, with install links
Manage standing links: list them and point one at an already-uploaded build
Handle testers and devices: read tester feedback, list and export iOS UDIDs, create device invite links
Manage webhooks: list, create, test and delete Slack, Discord or URL webhooks
Administer account and tokens: log in, log out, show the current account, list, create and revoke API tokens
When to use it: Useful when you build iOS or Android apps in an editor and want the assistant to publish a build and hand back an install link without switching to a browser or CLI. Also fits teams that distribute ad-hoc builds to testers and want to check signing, manage standing links or read feedback in the same conversation.
Requirements: Runs locally via npx, so Node.js 18 or newer is needed. A BetaDrop account is required; authenticate either with the BETADROP_TOKEN environment variable or by signing in through the server's login tool, which stores the token in a local config file. Optional BETADROP_API_URL and BETADROP_APP_URL variables override the default endpoints. Network access to the BetaDrop API.

Before you install

The API token (BETADROP_TOKEN or the one given to the login tool) is a live credential stored in a local config file; treat it as a secret. Tools can publish builds, delete builds and webhooks, revoke tokens, and repoint standing links, which emails followers. Creating a token shows its plaintext once. Permanent links and longer retention depend on a paid plan. Builds and metadata are sent to BetaDrop's servers.

Installation

In SourceWeft

Open BetaDrop in the dashboard and add it to a workspace.
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

[BetaDrop]

@betadrop/mcp

[npm version] [MCP Registry] [Node] [License: MIT]

"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.

23 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 with bd_live_... — save it somewhere safe, it's shown only once!)

Step 2 — Add the MCP Server to Your Editor

[!TIP] 🤖 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.

Claude Code

Run one command in your terminal:

This installs BetaDrop globally across all your Claude Code projects.
For a single project only, drop the -s user flag.

Verify it worked:

Start a new Claude Code session and type /mcp to confirm the connection.

Claude Desktop

Open your config file:

Add this inside the file:

json

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

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

Restart Claude Desktop. BetaDrop tools will appear in the 🔧 tools panel.

Cursor

Create .cursor/mcp.json in your project root:

json

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

{  "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.

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your project root:

json

{  "servers": {    "betadrop": {      "command": "npx",      "args": ["-y", "@betadrop/mcp"]    }  }}

{  "servers": {    "betadrop": {      "command": "npx",      "args": ["-y", "@betadrop/mcp"]    }  }}

Or add it globally:

Use Copilot in Agent mode to access BetaDrop tools.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

json

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

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

Zed

Add to your Zed settings file:

json

{  "context_servers": {    "betadrop": {      "command": {        "path": "npx",        "args": ["-y", "@betadrop/mcp"]      }    }  }}

{  "context_servers": {    "betadrop": {      "command": {        "path": "npx",        "args": ["-y", "@betadrop/mcp"]      }    }  }}

Antigravity (Google)

Open MCP settings from Settings → MCP Servers or edit the config file directly:

json

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

{  "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 👇

🚀 Try These Prompts

You don't need to memorize any tool names — just talk to your AI assistant naturally:

📦 Publishing Builds

Prompt	What Happens
`"Publish ./build/MyApp.ipa to BetaDrop"`	Uploads the IPA and returns an install link
`"Upload MyApp.apk with notes 'Fixed login crash on Android 14'"`	Publishes with release notes visible to testers
`"Push the latest IPA to BetaDrop, expire after 7 days"`	Sets a time-based expiry on the build
`"Upload MyApp.ipa and send me the install link"`	Returns a shareable OTA install URL

📋 Build History

Prompt	What Happens
`"Show my recent BetaDrop builds"`	Lists your latest builds across both platforms
`"List my iOS builds"`	Filters to iOS only
`"Show all expired builds on BetaDrop"`	Lists builds that have hit their expiry limit
`"Any expired Android builds?"`	Expired builds filtered by platform
`"Get the install link for my last build"`	Retrieves the shareable URL

🔑 Token Management

Prompt	What Happens
`"Show my BetaDrop API tokens"`	Lists all active tokens with abilities and expiry
`"Create a BetaDrop token for CI called 'GitHub Actions'"`	Creates a new token scoped for CI
`"Make a read-only token called 'QA Team'"`	Creates a token whose abilities are recorded as `read` only
`"Create a token that expires in 30 days"`	Auto-expiring token for temporary access
`"Revoke BetaDrop token abc-123"`	Permanently revokes a token

✅ Release Checks, Links and Devices

Prompt	What Happens
`"Will build/MyApp.ipa install from a link?"`	`betadrop_inspect` reads the profile and signing without publishing
`"Publish MyApp.ipa to the acme-beta standing link"`	Publishes and points the standing link testers already have at it
`"What did testers say about the last build?"`	Reads tester feedback
`"Export my test devices for the Apple portal"`	Returns the tab-separated devices file
`"Post new builds to this Slack webhook: https://hooks.slack.com/…"`	Creates a webhook formatted for Slack

👤 Account

🔁 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

Publishing Builds

Tool	What It Does
`betadrop_publish`	Upload an `.ipa` or `.apk` and get a shareable install link
`betadrop_upload_status`	Get the result (install link) of the most recent `betadrop_publish` upload. Takes no parameters — called automatically when a large build outruns the 90-second publish window

betadrop_publish parameters:

Parameter	Type	Required	Description
`filePath`	string	✅	Absolute path to the `.ipa` or `.apk` file
`name`	string		Override the app display name
`version`	string		Override the version string (e.g. `1.2.3`)
`buildNumber`	string		Override the build number
`bundleId`	string		Override the bundle / package ID
`notes`	string		Release notes shown on the install page
`expiryType`	string		`none` · `time` · `downloads` · `devices` · `combined`. `none` (a permanent link) requires a paid plan — see below
`expiryTimeDays`	number		Expire after N days (use with `time` or `combined`). Clamped to your plan's maximum build retention
`expiryDownloadLimit`	number		Expire after N downloads (use with `downloads` or `combined`)
`expiryDeviceLimit`	number		Expire after N unique devices (use with `devices` or `combined`)
`standingLink`	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. expiryTimeDays is clamped to your plan's maximum build retention on every plan. When either happens the server returns a retentionClamp object (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 no expiryTimeDays and it stays null even if your account default was clamped down. Current per-plan day ceilings live in src/lib/limits.json rather 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_status to fetch the link. A status file at ~/.betadrop/upload_status.json tracks the upload in real time.

Build History

betadrop_list_builds parameters:

Parameter	Type	Description
`platform`	string	`ios` or `android` — omit to list all
`status`	string	`active` · `expired` · `disabled` · `deprecated` · `latest`
`page`	number	Page number (default: `1`)
`perPage`	number	Results per page (default: `20`, max: `100`)

betadrop_list_expired_builds parameters:

Each result includes the build name, version, platform, file size, status, dates, and a shareable install link.

Token Management

Tool	What It Does
`betadrop_token_list`	List all your active (non-revoked) API tokens
`betadrop_token_create`	Create a new scoped token (plaintext shown only once!)
`betadrop_token_delete`	Permanently revoke a token by ID

betadrop_token_create parameters:

Parameter	Type	Required	Description
`name`	string	✅	Label for the token (max 100 chars)
`abilities`	string[]		`["publish"]`, `["read"]`, or `["*"]` (default: all)
`expiresInDays`	number		Token lifetime in days (1–365). Omit for no expiry

Abilities are enforced on every endpoint: a read token can list builds, read feedback and run betadrop_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

Standing Links

betadrop_publish also accepts standingLink to point one at the new build as it goes live.

Builds, Feedback and Devices

Tool	What It Does
`betadrop_delete_build`	Delete a build; its install link stops working
`betadrop_get_feedback`	Feedback testers left on a build
`betadrop_list_devices`	Registered iOS devices (UDIDs)
`betadrop_export_devices`	The devices file Apple's portal and fastlane `register_devices` accept
`betadrop_invite_device`	A link a tester opens on their iPhone to register it

Webhooks

Tool	What It Does
`betadrop_list_webhooks`	Webhooks on the account
`betadrop_create_webhook`	Send events to a URL, Slack or Discord (detected from the URL)
`betadrop_test_webhook`	Deliver a test event now and report the answer
`betadrop_delete_webhook`	Remove a webhook

Quick Help

⚙️ Configuration

Set these environment variables to override the defaults:

Variable	Default	Description
`BETADROP_API_URL`	`https://api.betadrop.app`	API server URL (for self-hosted)
`BETADROP_APP_URL`	`https://betadrop.app`	Frontend URL for install links
`BETADROP_TOKEN`	(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:

json

{  "mcpServers": {    "betadrop": {      "command": "npx",      "args": ["-y", "@betadrop/mcp"],      "env": { "BETADROP_TOKEN": "bd_live_xxx" }    }  }}

{  "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:

❓ Troubleshooting

"Tool not found" or no BetaDrop tools showing up?

Make sure Node.js 18+ is installed: node --version
Restart your editor after adding the MCP config
In Claude Code, run /mcp to check the server status
In 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_TOKEN env 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 lands
You can also watch ~/.betadrop/upload_status.json directly

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 .ipa only 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:


`@betadrop/cli` _source	`betadrop publish app.ipa` from your terminal. Prints the install link and a scannable QR code.
`betadrop-app/upload-action`	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
Report an Issue

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

Source: README.md at commit 423e9ac

Tools

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

Version history

v0.2.5LatestSep 16, 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

Other Drop integrations

drop.media

media.dropOfficial publisher

Host files and AI-generated images on drop.media and get public or expiring private links, via a remote OAuth-protected endpoint.

Streamable HTTPWeb executableAuth

Files & StorageCredential requiredOct 26, 2026

DropGone

com.dropgone

Local MCP server that lets an assistant send encrypted, expiring file links from allowed folders and check link availability without consuming a download.

STDIODesktop only

Files & StorageNot validated · the server did not startNov 8, 2026

DropGone

Published by GitHub account jbluedevil

DropGone lets an assistant send encrypted, expiring file links from allowed local folders and check link availability without consuming a download.

STDIODesktop only

Files & StorageNot validated · the package did not installNov 8, 2026

DropTrax

Published by GitHub account liamsloane

Find, preview and get buy links for songs sold directly by independent artists on DropTrax.

Streamable HTTPWeb executable

6 toolsNov 4, 2026

DropPerch domain expiry

Published by GitHub account webvoguetech

Checks live domain expiry, lifecycle stage, likely drop date and SSL certificate status over RDAP, with no account or API key.

STDIODesktop only

Web Search & Scraping4 toolsNov 10, 2026

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

OS	Path
macOS	`~/Library/Application Support/Code/User/mcp.json`
Windows	`%APPDATA%\Code\User\mcp.json`
Linux	`~/.config/Code/User/mcp.json`

OS	Path
macOS	`~/Library/Application Support/Zed/settings.json`
Linux	`~/.config/zed/settings.json`

OS	Path
macOS	`~/.gemini/antigravity-ide/mcp_config.json`
Windows	`%USERPROFILE%\.gemini\antigravity-ide\mcp_config.json`

Prompt	What Happens
`"Am I logged in to BetaDrop?"`	Shows your email, token details, and API URL
`"Log out of BetaDrop"`	Revokes the token server-side and clears local config