Another - Android Device Control

You have access to an Android device through the Another MCP server. Use these tools to see what's on screen, interact with the device, and automate tasks.

Setup

The Another desktop app must be running with MCP Server enabled (on by default in Settings).

Add to your MCP settings (Claude Code, Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "another": {
      "type": "http",
      "url": "http://localhost:7070/mcp"
    }
  }
}

Workflow

Always follow this order:

1. List devices to see what's available
2. Connect to establish a control session
3. Screenshot to see the current screen state
4. Act using touch, text, buttons, swipe, etc.
5. Screenshot again to verify the result
6. Disconnect when done

Available Tools

Device Management

Observation

Input

Apps & Shell

WiFi

Coordinate System

Touch, swipe, and scroll tools use normalized coordinates from 0.0 to 1.0:

• (0.0, 0.0) = top-left corner
• (1.0, 1.0) = bottom-right corner
• (0.5, 0.5) = center of screen

Common Patterns

Tap on something

another_send_touch { action: "down", x: 0.5, y: 0.5 }
another_send_touch { action: "up", x: 0.5, y: 0.5 }

Tap, then verify

1. another_take_screenshot  (see what's on screen)
2. another_send_touch       (tap where you need to)
3. another_take_screenshot  (verify the result)

Type into a field

1. Tap the input field with another_send_touch
2. another_send_text { text: "hello world" }

Scroll down a page

another_send_scroll { x: 0.5, y: 0.5, dx: 0.0, dy: -1.0 }

Swipe to go back or navigate

another_swipe { from_x: 0.0, from_y: 0.5, to_x: 0.5, to_y: 0.5 }

Navigate with buttons

another_press_button { button: "home" }
another_press_button { button: "back" }
another_press_button { button: "recents" }

Open an app and interact

1. another_launch_app { package: "com.android.chrome" }
2. Wait briefly, then another_take_screenshot
3. Interact as needed

Find an element on screen

Take a screenshot, examine it to identify positions, then use the coordinates to interact. Screenshots are the primary way to understand what's visible on the device.

Run a shell command

another_shell { command: "pm list packages" }
another_shell { command: "dumpsys battery" }
another_shell { command: "settings get system screen_brightness" }

Tips

• Always screenshot first before interacting. You need to see the screen to know where to tap.
• Screenshot after actions to confirm they worked.
• Use shell commands for things that don't need the screen (checking battery, listing packages, getting device info).
• Swipe duration defaults to 300ms. Increase duration_ms for slower, more deliberate swipes.
• Connect before acting. Tools like pressbutton, sendtext, sendtouch, swipe require an active connection via anotherconnect_device.
• **listdevices, shell, takescreenshot, wifi_* tools** work without a scrcpy connection, they only need adb.