BetaDrop

@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, look up release history and manage API tokens through ordinary prompts — no browser tab, no CLI, no leaving the editor.

claude mcp add betadrop -s user -- npx -y @betadrop/mcp

11 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

1. Sign up or log in at betadrop.app
2. Go to Settings → Developer
3. 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 mcp add betadrop -s user -- npx -y @betadrop/mcp

claude mcp list

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

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

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

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

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

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

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

📋 Build History

🔑 Token Management

👤 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

Eleven tools across four areas. You never call these by name — the assistant picks them.

Authentication

Publishing Builds

betadrop_publish parameters:

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:

betadrop_list_expired_builds parameters:

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

Token Management

betadrop_token_create parameters:

Abilities are recorded on the token and shown by betadrop_token_list; publishing builds requires the publish ability. Do not treat a read token as a hard security boundary across every endpoint — scope it to a plan, and revoke tokens you no longer hand out.

⚠️ The plaintext token is shown exactly once at creation. Copy it immediately!

Quick Help

⚙️ Configuration

Set these environment variables to override the defaults:

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

📚 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