Claude Android connectorWhat Claude can do in your Android account.
The Claude Android connector exposes 9 tools. 2 read or wait, 6 act on the screen, 1 is described nowhere. Below: what Claude can do on a phone or emulator from Claude Desktop, what you must install first, and why the publisher urges a test device.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your mobile and QA team
Android-MCP is an open-source desktop extension from CursorTouch that lets Claude operate an Android device like a person would: tapping, typing, swiping and reading notifications. It runs on your computer, talks to the phone through Google's debugging bridge, and works only in Claude Desktop.
Walk through an app in plain words. You describe the path, open settings, change the language, go back, and Claude chains Click, Swipe and Press to follow it on the screen.
Fill forms during manual QA. Type enters test data into fields and can clear them first, while Wait gives slow screens time to load before the next gesture.
Check that messages arrive. Notification reads what the notification shade shows, so a tester can confirm that a push from the app under test came through.
What it will not do: nothing happens without you. The tools run while Claude answers, never on their own when a notification lands. The publisher counts two to four seconds between actions, so it is not a speed tool. And it acts on a real screen: the README warns that it can perform arbitrary UI actions and should run on emulators or test devices. For phone-triggered scenarios, see the Android Make integration.
The vocabulary in one minute
Six words you will meet while plugging Android-MCP in.
- Connector
- The link you set up once between Claude and something you already own, here an Android phone or emulator, so Claude can work on it while it answers.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The permission you grant so Claude can act. Here there is no sign-in screen: the device's ADB authorization plays that role.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude drive something outside itself, here an Android device.
- ADB
- Android Debug Bridge, Google's command-line link to a phone or emulator. Android-MCP needs it installed and the device authorized.
Connect Android to Claude in three steps
- 01
Find Android-MCP in Claude
In Claude Desktop's settings, open Customize, then Connectors, and look for Android-MCP in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first before members can add it.
- 02
Start the connection
Click Connect on its row to add the extension to Claude Desktop. If it misbehaves later on, use Disconnect and add it again from the same row, then retry.
- 03
Review what you are granting
Read what the extension is allowed to do before you confirm. Here the gatekeeper is the phone itself: the publisher requires it to be connected and authorized for ADB, and without that the computer, and so Claude, reaches nothing.
The 9 Claude Android connector tools, sorted by what they do
Android-MCP gives Claude 9 tools: 2 that read your account, 6 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it does on the screen, and what no official source describes. Names stay exactly as Claude shows them.
- 2 read
- 6 write
- 1 not documented
What Claude reads (2)
2 toolsTwo tools that look at the device or simply wait, without touching the screen.
Notification
Reads the notifications currently visible on the device, so Claude knows what the phone is showing in its notification shade.
Wait
Holds still for a set duration between two gestures, giving an app time to load or an animation time to finish. Nothing on the phone is touched while it runs.
What Claude changes (6)
6 toolsSix gestures that act on the device. No specific confirmation is documented for them.
Click
Approval: see the ruleTaps the screen at the coordinates given, exactly like a finger on a button or a field.
LongClick
Approval: see the rulePresses and holds at a given point of the screen, the gesture Android uses for context menus and drag handles.
Swipe
Approval: see the ruleSlides from one point of the screen to another, to scroll a list, flip a page or dismiss a card.
Type
Approval: see the ruleEnters text at the given coordinates, into a search bar or a form field, and can clear what was already written first.
Drag
Approval: see the ruleDrags from one point to another, the gesture for reordering items, moving a slider or pulling an icon across the screen.
Press
Approval: see the rulePresses the device's keys, such as Back or Volume Up, the buttons that are not drawn on screen.
Not documented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and this page will not guess from a name.
Snapshot
The directory lists this name and nothing more. The publisher's README describes its tools under other names, and none of them is called Snapshot, so this page does not say what it returns or does.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on something it reaches for you. The request shows up in the conversation, when it matters.
The publisher describes no confirmation of its own for the six gestures, so Claude's default rule covers them. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can cap what a connector may do for the whole organization. That setting binds everyone. Claude reaches only the device you connected and authorized, nothing else on the network.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. Connector by connector, the answer is published nowhere: a real gap in the catalogue.
The general rule is published: desktop extensions install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization first. The directory sheet lists Claude Desktop as the only surface here, and it is the only place showing the current state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a notification arrives or an app crashes.
Only the publisher documents this connector, through its GitHub README: no Claude help article covers it. The tool list is an observed floor, not a promise, and the README itself names a few tools the sheet does not carry. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee their behavior. That weighs more for an extension that acts on a phone. For other connectors, browse the Integrations hub.
Need help connecting Android-MCP to Claude?
A person reads every message.
