# thecombatwombat/replicant-mcp [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/thecombatwombat/replicant-mcp  
**GitHub Stars:** 18  
**npm Downloads (last month):** 496  
**Views:** 11  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/thecombatwombat-replicant-mcp

## Description
Android MCP server for AI-assisted Android development. Build APKs, launch emulators, manage devices, automate UI, and analyze logs through natural conversation.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "replicant-mcp": {
    "command": "npx",
    "args": ["-y","replicant-mcp"],
    "env": {
      "ANDROID_HOME": "",
      "REPLICANT_CONFIG": "",
      "REPLICANT_LOG_LEVEL": "",
      "REPLICANT_LOG_FORMAT": ""
    }
  }
}
```

**Requires environment variables:** `ANDROID_HOME`, `REPLICANT_CONFIG`, `REPLICANT_LOG_LEVEL`, `REPLICANT_LOG_FORMAT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What thecombatwombat/replicant-mcp does

thecombatwombat/replicant-mcp MCP server exposes Android development operations to MCP-compatible AI clients. It connects the assistant to an Android project with a Gradle wrapper, the Android SDK, adb, emulators, and connected devices. The server is listed in the Developer Tools category and is intended for build, test, debugging, and UI-driven verification work.

Build and test operations cover APKs and app bundles, unit tests, instrumented tests, and inspection of project modules, variants, and tasks. A baseline comparison can be used for regression detection. Device and application operations include listing devices, selecting an active device, reading device properties, installing or removing packages, launching or stopping apps, and clearing app data.

## How it works

The server runs as a Node.js process and communicates with an MCP client. The documented client configurations launch it with `npx -y replicant-mcp`. Underlying Android work depends on tools such as `adb`, `emulator`, and the project’s `gradlew` script.

thecombatwombat/replicant-mcp uses progressive disclosure: responses provide summaries first, with additional details available when needed. For interface automation, it prioritizes the Android accessibility tree and can locate elements by text or spatial proximity. It also supports taps, text entry, and screenshots. Logcat can be filtered by package, tag, severity, and time instead of returning an entire unfiltered stream.

## Setup and configuration

Install Node.js 18 or newer, then install the package globally:

```bash
npm install -g replicant-mcp
replicant doctor
```

The Android SDK must be installed for emulator and build workflows, with `adb` and `emulator` on `PATH`. A project build also needs a usable `gradlew`. If the SDK binaries are not on `PATH`, set `ANDROID_HOME`; the README gives macOS and Linux examples.

Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Codex CLI are documented setup targets. Each uses the `replicant-mcp` package as an stdio process. Advanced configuration can be selected with `REPLICANT_CONFIG`. Logging is controlled with `REPLICANT_LOG_LEVEL` values such as `error`, `warn`, `info`, or `debug`, and `REPLICANT_LOG_FORMAT=json` enables structured output on stderr.

## Tools and capabilities

The documented capability groups are:

- Build APKs and bundles, run unit or instrumented tests, inspect Gradle targets, and compare test results with a baseline.
- Create, start, stop, wipe, and snapshot Android emulators.
- List connected devices, choose an active device, and inspect device properties.
- Install, uninstall, launch, stop, and reset application data.
- Filter and inspect logcat output.
- Find accessibility elements, search by proximity, tap, enter text, and capture screenshots.
- Run environment checks through `replicant doctor` and use configurable logging.

## Limitations and notes

thecombatwombat/replicant-mcp depends on the local Android toolchain, so it cannot replace the SDK, adb, emulator binaries, or a project build setup.

Video capture is not currently listed as an available feature; start/stop recording and duration-based capture are described as planned work. Custom build commands and automatic `gradlew` detection are also planned rather than current capabilities. Review the project’s security documentation before allowing an agent to operate on development devices, and use `replicant doctor` when checking the environment.

_Full upstream README: https://allmcps.com/mcp/thecombatwombat-replicant-mcp/readme_