MeshCentral Android Agent connects an Android device to a MeshCentral server for remote monitoring and support. It is a native Kotlin application and is separate from the MeshCentral agents used on Windows, Linux, macOS, and FreeBSD.
Pair a device by scanning a MeshCentral QR code, opening an mc:// pairing
link, or entering the link manually. After enrollment, the app maintains an
authenticated connection to the server and can:
- Report device, network, storage, and battery information.
- Share the device screen after Android MediaProjection consent.
- Browse and transfer media and files available to the app.
- Receive server notifications and a limited set of console commands.
- Approve or reject MeshCentral push-based two-factor authentication requests.
Remote desktop is currently view only. The app can stream the display, but it cannot tap, swipe, type, or otherwise control the device. Android displays a foreground notification while screen sharing is active, and the user can deny or stop capture at any time.
Install MeshAgent for Android from Google Play.
Or download the APK or AAB from the latest release.
- Android 6.0 (API 23) or later.
- A MeshCentral server configured to enroll Android agents.
- Android Studio or JDK 17 and an Android SDK for local development.
Open the repository in Android Studio, or build and test it from the repository root:
.\gradlew.bat assembleDebug testDebugUnitTest lintDebugThe debug APK is generated under app/build/outputs/apk/debug/. Production
releases require a dedicated signing keystore; see the release guide below.
- Documentation site - published project documentation.
- Documentation home - introduction, installation, key capabilities, and links to all project resources.
- Repository overview - architecture, components, project configuration, and development notes.
- Remote desktop - screen-capture flow, consent, encoding, and Android platform limitations.
- Tunnel authentication - control-channel authentication, certificate pinning, and relay tunnel trust.
- Push two-factor authentication - FCM request validation, approval flow, and lifecycle behavior.
- Creating a release - versioning, signing, GitHub Actions, and publishing APK and AAB artifacts.