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