TapTry

taptry

Turn an Android build into a link anyone can run in their browser - no install, no sideloading. From your terminal, from CI on every pull request, or from your coding assistant.

npx taptry upload app/build/outputs/apk/release/app-release.apk
# Uploading app-release.apk (18.2 MB)…
# Created My Game - https://taptry.in/app/my-game
# Waiting for the malware scan and checks (this can take a few minutes)…
#   Checking for malware…
#   Ready
# https://taptry.in/app/my-game

Takes .apk, .aab, .apks, .xapk and .apkm, up to 500MB. Every upload is malware-scanned before its link works. Needs Node 20+; no dependencies.

Setup

1. In TapTry, open Settings > API keys and create a key.
2. Either save it on your machine - npx taptry login - or set TAPTRY_API_KEY (what CI should do).

CLI

taptry upload <file> [--name <name>] [--ref <ref>] [--unlisted | --private] [--no-wait] [--timeout <s>] [--json]
taptry status <app> | --ref <ref>
taptry list [--ref <ref>]
taptry delete <app> | --ref <ref> [--yes]
taptry login | logout | whoami
taptry mcp

• --ref is your own id for an app, e.g. github:me/game#42. Uploading again with the same ref replaces that app's file and keeps its link - use it for anything you upload repeatedly.
• Visibility: public by default (on your TapTry profile, anyone can run it). --unlisted: listed nowhere, and the link printed is a secret link only the people you send it to can open. --private: only you.
• upload waits for the checks by default and prints the link on stdout, so URL=$(taptry upload app.apk) works. --json prints the whole result.
• delete asks first; without a terminal it needs --yes.

Exit codes: 0 ok · 1 error (network, auth, refused request) · 2 bad usage · 3 the app failed its checks (malware, not an app, …) · 4 timed out waiting for the checks.

GitHub Action: a preview link on every pull request

Each pull request gets one TapTry app and one comment with its link, updated on every push and deleted when the PR closes. Previews are unlisted by default: anyone with the link in the PR can run them, and they never show up on your TapTry profile.

# .github/workflows/taptry-preview.yml
name: TapTry preview
on:
  pull_request:
    types: [opened, synchronize, reopened, closed]

permissions:
  contents: read
  pull-requests: write

jobs:
  preview:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        if: github.event.action != 'closed'
      - uses: actions/setup-java@v4
        if: github.event.action != 'closed'
        with:
          distribution: temurin
          java-version: 17
      - name: Build
        if: github.event.action != 'closed'
        run: ./gradlew assembleDebug
      - uses: Romildoescoding/taptry-cli@v1
        with:
          api-key: ${{ secrets.TAPTRY_API_KEY }}
          file: app/build/outputs/apk/debug/app-debug.apk

Add your key as the repository secret TAPTRY_API_KEY. Pull requests from forks don't get secrets, so their previews are skipped with a warning.

Outputs: url, app-id, slug, status, ready.

Outside pull requests (e.g. on: push to main), it keeps one app per branch: github:<repo>@main.

MCP server: "build it and give me a link"

taptry mcp is a Model Context Protocol server for Claude Code, Cursor, Claude Desktop and other MCP clients. Tools: upload_app, get_status, get_link, list_apps, delete_app. The assistant is told to ask before uploading or deleting, and delete_app refuses unless confirm: true is passed.

Claude Code

claude mcp add taptry -e TAPTRY_API_KEY=tt_your_key -- npx -y taptry mcp

Cursor (~/.cursor/mcp.json) or Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "taptry": {
      "command": "npx",
      "args": ["-y", "taptry", "mcp"],
      "env": { "TAPTRY_API_KEY": "tt_your_key" }
    }
  }
}

After taptry login you can leave out the env block.

Claude Code plugin - the MCP server and the TapTry skill in one install (set TAPTRY_API_KEY in your environment first):

/plugin marketplace add Romildoescoding/taptry-cli
/plugin install taptry@taptry

Let your assistant test the app on a real device

The MCP server can also run your uploaded app on a cloud Android device and let the assistant use it: start_session, then screenshot (it sees the screen) and get_ui (the elements, with coordinates), tap (by label or position), type_text, press_key, swipe, get_logs (crashes and recent log lines) and end_session. So "upload the build, open it, sign up with a test account and tell me if anything crashes" works end to end. Each session uses one of your runs and ends after 5 minutes without a call; at most 2 run at once.

API

Everything here wraps TapTry's public HTTP API at https://api.taptry.in/api/v1 (bearer-token auth with the same key). A full reference for using it directly is coming to TapTry's docs.

License

MIT