Push a build to your testers

Send a signed APK over the air from your editor or your CI, with a SHA-256 check on every download.

Your testers get a push notification and install your new build, without a cable or a file transfer.

Before you begin

Test Nexus on your Android device, and a Test Nexus account.
A Platinum subscription. Remote Install is a Platinum feature, and so is the pairing screen — so each tester needs Platinum on their own device too, not only you.
A signed APK of 300 MB or less.
Node.js, which provides the npx command, if you want to push from your editor or your CI.
Each tester needs Test Nexus, the Install unknown apps permission, and notifications left on — without those the build cannot install and the alert never arrives.

Open Remote Install from the App Hub and tap the add button.
Name the project. Test Nexus shows you an API key once. Copy it and store it somewhere safe, such as your CI environment variables or a password manager.
Find the Project ID in Project Settings. You need both values to push a build.

Install the Test Nexus MCP server: claude mcp add testnexus -- npx -y @twocan/testnexus-mcp
Give the server your API key and Project ID.
Ask your MCP client to push your signed APK. The server handles the upload, the metadata and the notification to your team.

Ask each teammate to open Remote Install and tap Pair with a Project. They generate a six-digit code and send it to you.
Open your project, tap Add Member, and enter their email and code. The code expires after five minutes. A project holds up to 10 members.
Each member chooses auto-install or manual confirmation on their own device.

Your first build waits for approval. Open the project and tap Review signer to approve the signing key. You do this once.
After that, every pushed build sends a push notification to each member who has notifications enabled. Tapping it shows download speed, time remaining and progress, and it can be cancelled at any point.
Each build is checked with a SHA-256 hash, so a file that changed in transit does not install.
Build history keeps the three most recent builds, so you can roll back to one of those. Older builds are removed automatically.

API keys expire after 90 days. Rotate the key from Project Settings to reset the clock.
Project Settings shows when the key was last used, so unexpected activity is visible.
Removing a team member from the Team section takes effect right away.

Push a build, then check a tester device: the notification arrives and the build appears in the build history for that project.
If nothing arrives, check the pairing was accepted, the signer was approved, and that the tester allowed notifications and Install unknown apps.