Log inSubmit server
Replicant MCP logo

Replicant MCP

by thecombatwombat

Controls Android builds, emulators, devices, apps, UI flows, and log analysis through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Replicant MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "thecombatwombat-replicant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "replicant-mcp"
      ],
      "env": {
        "ANDROID_HOME": "YOUR_VALUE_HERE",
        "REPLICANT_CONFIG": "YOUR_VALUE_HERE",
        "REPLICANT_LOG_LEVEL": "YOUR_VALUE_HERE",
        "REPLICANT_LOG_FORMAT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y replicant-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 23d ago.

Overview

thecombatwombat/replicant-mcp MCP server connects AI assistants to an Android development environment through Model Context Protocol tools. It can build and test projects, manage emulators and connected devices, install and launch apps, automate interfaces through accessibility data, and filter logcat output. Install it with npm and run it through an MCP client using npx; Android SDK tools, adb, and emulator must be available. Reach for it when an agent needs to execute and inspect Android development workflows rather than only edit source code.

Use cases

  • Build and install an Android debug APK
  • Run instrumented tests on an emulator
  • Navigate an app through accessibility controls
  • Inspect filtered logcat output after a crash
  • Create and manage emulator snapshots

Key features

  • APK and app bundle builds
  • Unit and instrumented test execution
  • Emulator and device management
  • Accessibility-first UI automation
  • Filtered logcat analysis
  • Environment diagnostics and configurable logging

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · replicant-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars18Stargazers on the source repository.
npm downloads496Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity11 viewsConfig copies, upvotes, and views on AllMCPs.

How Replicant MCP works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Replicant MCP

thecombatwombat/replicant-mcp is an MCP server that connects AI assistants to an Android development environment through adb, emulators, and Gradle projects. Its main tools build and test apps, manage devices and application packages, automate interfaces through accessibility data, capture screenshots, and filter logcat for debugging.

Install it with Node.js 18 or newer by running `npm install -g replicant-mcp`, then verify the environment with `replicant doctor`. The Android SDK, adb, and emulator must be available for the corresponding workflows.

Yes, Cursor is documented as a supported client. Add an `mcpServers.replicant` entry to the global `~/.cursor/mcp.json` or project-level `.cursor/mcp.json`, using `npx` with `-y replicant-mcp`.

It requires Node.js 18 or newer, and Android workflows require the Android SDK with `adb` and `emulator` on `PATH`. Projects being built also need a `gradlew` wrapper; `ANDROID_HOME` can identify the SDK when its binaries are not already on `PATH`.

Yes, it can find UI elements through the accessibility tree, search by spatial proximity, tap controls, enter text, and take screenshots. It can also install and launch the app on an active emulator or connected device.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewReplicant MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/thecombatwombat-replicant-mcp?style=directory)](https://allmcps.com/mcp/thecombatwombat-replicant-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/thecombatwombat-replicant-mcp"><img src="https://allmcps.com/api/badge/thecombatwombat-replicant-mcp?style=directory" alt="Replicant MCP on AllMCPs" /></a>