# Ramus Android

Hands a coding agent a throwaway Android emulator in the cloud: launch an APK, tap, type, screenshot, pull logs. Useful for checking a build from the chat.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 4
- Author: ramus-dev
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ramus-dev/android-use
- Updated: 2026-10-05
- HTML: https://affpapa.org/en/nevibecode/mcp/ramus-android

## What it does

The server wires your agent to a real Android emulator on stock Google images, running on Ramus hardware and streamed over WebRTC. Tools come under the `android_*` prefix. An agent can open a session from a demo app or a pull request, grab a snapshot of the UI tree, tap a referenced element, enter text, press a key, wait, take a screenshot, read logs and share the session. You can watch the same device in a browser and take over the controls.

The bundled skill teaches the observe, act, verify loop. Snapshot the tree first, act on one element, then confirm the outcome. Skip that and the agent pokes the screen blindly. The remote server speaks Streamable HTTP, so no local process is needed; uploading a local APK and the dev loop go through the `ramus-cli` CLI.

A Ramus account covers it (free during alpha), or you can try the CLI for 60 minutes without signing up. The remote endpoint wants an API key from your account settings: there is no `Authorization` header, no access. Android only, and it is meant for apps you built or are allowed to test.

## Requirements
- Remote server: `https://api.ramus.dev/api/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http ramus-android https://api.ramus.dev/api/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add ramus-android --url https://api.ramus.dev/api/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "ramus-android": {
            "url": "https://api.ramus.dev/api/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "ramus-android": {
            "type": "http",
            "url": "https://api.ramus.dev/api/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http ramus-android https://api.ramus.dev/api/mcp
```

## When to use it
- walk a fresh APK build through its screens without starting an emulator by hand
- exercise a pull request build before merging
- snapshot the UI tree and locate the right element to tap
- collect screenshots and crash logs in a single run
- hand a live device session to a teammate in the browser

## Example prompts
- Start an Android session from `app-debug.apk`, open the login screen and send me a screenshot.
- Tap the pay button, snapshot the UI tree and check whether an error message appeared.
- Open a session from the pull request, run through onboarding and pull the logs.

## Similar
- [mobile-mcp](https://affpapa.org/en/nevibecode/mcp/mobile-mcp.md) — MCP server · ★ 10025
- [mobilerun](https://affpapa.org/en/nevibecode/mcp/mobilerun.md) — MCP server · ★ 9833
- [e2e](https://affpapa.org/en/nevibecode/mcp/e2e.md) — MCP server · ★ 11962
- [XcodeBuildMCP](https://affpapa.org/en/nevibecode/mcp/xcodebuildmcp.md) — MCP server · ★ 6511
- [ShipSwift](https://affpapa.org/en/nevibecode/mcp/shipswift.md) — MCP server · ★ 3244
- [agent-device](https://affpapa.org/en/nevibecode/mcp/agent-device.md) — MCP server · ★ 5158

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md