@betadrop/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BETADROP_TOKEN | No | Token for CI — skips the local config file. | |
| BETADROP_API_URL | No | API server URL (for self-hosted). | https://api.betadrop.app |
| BETADROP_APP_URL | No | Frontend URL for install links. | https://betadrop.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| betadrop_whoamiA | Check authentication status and show the active account and BetaDrop server details. |
| betadrop_loginA | Configure API authentication with a BetaDrop token. Validates the token against the server and saves credentials to the shared CLI config. |
| betadrop_logoutA | Revoke the active token on the server and clear local credentials. |
| betadrop_publishB | Publish an iOS (.ipa) or Android (.apk) build to BetaDrop. |
| 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. |
| betadrop_list_buildsB | List recent builds published to BetaDrop, optionally filtered by platform and status. |
| betadrop_list_expired_buildsA | List all expired builds on BetaDrop. Shortcut for listing builds with status 'expired'. Shows expiry reason and details. |
| betadrop_helpA | Get a quick reference of all available BetaDrop MCP tools, their inputs, and example prompts. |
| betadrop_token_listA | List all active CLI tokens for the current account. |
| betadrop_token_createA | Create a new CLI token. The plaintext token is shown exactly once — copy it immediately. |
| betadrop_token_deleteA | Revoke a CLI token by its ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.