MCP servers · 36 tools · version 0.2.0
Android Studio bridge
Gradle builds, run and debug, adb and logcat in Android Studio.
An Android Studio plugin that runs an MCP server inside the IDE, with its own stdio bridge for Claude. Written in plain Java against Android Studio's own APIs, with no third-party code.
Free for 30 days on each computer, every tool, no sign-up. Then a key: personal use is paid after the trial. Setup also installs the MCZ MCP Manager, which shows every MCZ MCP server's licence and buys or installs keys in one click.
Several sessions at once, without tripping over each other
The Android Studio bridge is a bridge: it controls access for every AI connection on the PC, gives each chat its own Android Studio window and keeps the other chats out of it, so several AIs work at the same time without getting in each other's way. One server per Android Studio process; every tool takes the project, and a session claims a project (a lease) before working on it, so each AI session works in its own project window and another session gets "In use" instead of a clash.
What it does
- Gradle sync and builds, following the log while they run
- Build errors parsed from Kotlin, javac, CMake/clang and AAPT
- Run configurations; run and debug (Java/Kotlin and native LLDB): stepping, locals, evaluate, breakpoints
- Devices, adb and filtered logcat
- Open files, unsaved editors, and any IDE action by id
Manual: Android Studio bridge manual (also as PDF) · Getting started with the MCP servers
Requirements
- Windows 11 with Android Studio 2026.1 (Quail) or later; it uses Android Studio's own Java, nothing extra to install
- Per-user setup, no administrator rights; close Android Studio while it installs
- An MCP client: Claude Desktop (set up for you), Claude Code or any other client that speaks MCP
Set up
Setup installs the plugin and registers "android-studio" in Claude Desktop. Restart Claude Desktop afterwards and ask Claude to use it; license_status shows the trial days left.
Licence
A computer joined to a domain or Entra ID counts as commercial. Each key is tied to the computer's Machine ID, which
license_status and the MCZ MCP Manager show. Install a key with license_install from Claude, in the MCZ MCP
Manager, or with the server's --license command. Licence terms. Several computers: order with a list of Machine IDs.