MODEL CONTEXT PROTOCOL (MCP) SERVER
BetaDrop MCP connects Cursor, Claude, and Copilot to BetaDrop.
Publish builds, track releases, and manage tokens using pure natural language.
BetaDrop MCP demo prompts:
Add the @betadrop/mcp server to my global mcp.json config
Log me in to BetaDrop with my API token
Publish ./build/MyApp.ipa to BetaDrop
Get the install link for the latest uploaded APK
Create a new scoped API token for CI/CD
From installation to your first AI-driven build publish in under 2 minutes.
Sign up or log in at betadrop.app. Go to Settings → Developer → API tokens. Click Create Token, give it a name (e.g. "My IDE"), and copy the token.
Use your AI assistant to automatically install and configure the MCP server.
AI-assisted installation
You're already driving an AI assistant (Cursor Composer, Claude, Copilot, or Antigravity), so there's no config file to edit by hand. Paste one of these prompts into the chat:
"Add the @betadrop/mcp server to my global Cursor mcp.json config""Add the @betadrop/mcp server to my Antigravity mcp_config.json""Add the @betadrop/mcp server to my workspace .vscode/mcp.json""Add the @betadrop/mcp server to my Claude Desktop config"The assistant locates, creates, or updates the config file for you. Restart or refresh your editor afterwards. MCP servers are discovered at startup.
{
"mcpServers": {
"betadrop": {
"command": "npx",
"args": ["-y", "@betadrop/mcp"]
}
}
}Use natural language to tell your AI assistant exactly what you want to do.
You don't call these by name. Describe the outcome and the assistant picks the tool. The full argument reference for all ten is in the MCP server docs.
betadrop_publishbetadrop_list_buildsbetadrop_list_expired_buildsbetadrop_loginbetadrop_logoutbetadrop_whoamibetadrop_token_createbetadrop_token_listbetadrop_token_deletebetadrop_helpAdd a betadrop entry to Cursor's mcp.json — "command": "npx", "args": ["-y", "@betadrop/mcp"] — either in .cursor/mcp.json for one project or in the global config, then refresh Cursor, since MCP servers are discovered at startup. Nothing installs ahead of time: npx fetches the package on first run, and Node 18 or newer is the only requirement. You can also paste the install prompt from this page into Cursor's chat and let it edit the config for you.
Yes. One command registers it for every project: claude mcp add betadrop -s user -- npx -y @betadrop/mcp. Claude Desktop uses the same server through an mcpServers entry in its config file. In both cases the server is a local process speaking stdio to the client, and it shares credentials with the BetaDrop CLI, so a machine where betadrop login has already run is authenticated with nothing further to configure.
The MCP server resolves credentials exactly the way the CLI does: a BETADROP_TOKEN environment variable first, then the shared credentials file that betadrop login writes. If you have logged in with the CLI on the same machine there is nothing to set up. Otherwise, create a token under Settings → Developer → API tokens and ask the assistant to run betadrop_login with it — the token is validated against the server before it is saved, and saving it also logs the CLI in.
No. The build never passes through the assistant or the model. The MCP server runs locally on your machine, reads the .ipa or .apk from disk, and uploads it directly to BetaDrop. What the assistant sees is the tool call and the result: build metadata and the install link. That is also why betadrop_publish takes an absolute file path — the server does not necessarily share a working directory with your editor.
Stop context-switching. Stay in your code and let your AI assistant handle the distribution.
npx -y @betadrop/mcp