replicant-mcp

io.github.thecombatwombatPublished by GitHub account thecombatwombatv1.6.7Updated Oct 24, 2026

Android MCP server for AI-assisted development. Build, test, emulate, and automate.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.thecombatwombat/replicant-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account thecombatwombat for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.thecombatwombat%2Freplicant-mcp.svg)](https://sourceweft.com/mcp/io.github.thecombatwombat%2Freplicant-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an AI assistant build, test, install, and drive Android apps on emulators or connected devices.

What you can do: An Android development MCP server that builds APKs and bundles, runs unit and instrumented tests, and manages emulators (create, start, stop, wipe, snapshots). It installs, launches, and clears app data, filters logcat output, and performs accessibility-first UI automation such as finding elements by text, tapping, typing, and taking screenshots. It also reports environment health and uses progressive disclosure to keep token usage low.
When to use it: Useful when an assistant should work inside an Android project: compiling and testing builds, reproducing UI flows on an emulator or device, reading filtered logs, and debugging crashes without copy-pasting command output. Best for developers who already have an Android toolchain set up.
Requirements: Runs locally via npx, so Node.js 18+ is needed. Requires the Android SDK with adb and emulator on PATH, or ANDROID_HOME set; build tools need a project with gradlew. Optional environment variables REPLICANT_CONFIG, REPLICANT_LOG_LEVEL, and REPLICANT_LOG_FORMAT control configuration and logging. Desktop only.

Before you install

The server drives real devices and emulators: it installs and uninstalls apps, clears app data, wipes emulators, and sends taps and text input, so actions can change or delete state on the target device. It writes artifacts under a .replicant directory, which the documentation flags for privacy considerations. No credentials are declared.

Installation

In SourceWeft

Open replicant-mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

replicant-mcp

Let AI build, test, and debug your Android apps.

[CI] [npm] [Node.js] [License: MIT] [Ask DeepWiki] [replicant-mcp MCP server]

replicant-mcp is a Model Context Protocol server that gives AI assistants like Claude the ability to interact with your Android development environment. Build APKs, launch emulators, install apps, navigate UIs, and debug crashes—all through natural conversation.

Demo

[replicant-mcp demo]

Why replicant-mcp?

Without replicant-mcp	With replicant-mcp
"Run `./gradlew assembleDebug`, then `adb install`, then `adb shell am start`..."	"Build and run the app"
Copy-paste logcat output, lose context	AI reads filtered logs directly
Screenshot → describe UI → guess coordinates	AI sees accessibility tree, taps elements by text
5,000 tokens of raw Gradle output	50-token summary + details on demand

Features

Category	Capabilities
Build & Test	Build APKs/bundles, run unit and instrumented tests, list modules/variants/tasks, test regression detection with baseline comparison
Emulator	Create, start, stop, wipe emulators; save/load/delete snapshots
Device Control	List connected devices, select active device, query device properties
App Management	Install, uninstall, launch, stop apps; clear app data
Log Analysis	Filter logcat by package, tag, level, time
UI Automation	Accessibility-first element finding, spatial proximity search, tap, text input, screenshots
Diagnostics	Environment health checks via `replicant doctor`; structured logging with configurable level and format

Coming Soon

Custom build commands (project-specific overrides, auto-detect gradlew)
Video capture (start/stop recording, duration-based capture)

Quick Start

Prerequisites

Node.js 18+
Android SDK with adb and emulator in your PATH
An Android project with gradlew (for build tools)

bash

node --version      # Should be 18+adb --version       # Should show Android Debug Bridge versionemulator -version   # Should show Android emulator version

node --version      # Should be 18+adb --version       # Should show Android Debug Bridge versionemulator -version   # Should show Android emulator version

Installing prerequisites (macOS via Homebrew)

If you don't already have these tools, install them with Homebrew:

Node.js 18+

Physical-device only — just adb, sufficient if you never run an emulator:

adb lands directly on your PATH; no further config needed.

Full Android SDK — needed for emulator workflows or building APKs via the gradle-* tools. Run the steps in order:

bash

# 1. JDK — required by sdkmanager itself, and by the gradle-* toolsbrew install --cask temurin@17
# 2. cmdline-tools (provides sdkmanager)brew install --cask android-commandlinetools
# 3. Set ANDROID_HOME and create the directory BEFORE running sdkmanager,#    otherwise sdkmanager has no install target.export ANDROID_HOME="$HOME/Library/Android/sdk"mkdir -p "$ANDROID_HOME"
# 4. Accept all SDK licenses first, then install packages.#    `sdkmanager --install` aborts on unaccepted per-package licenses#    (e.g. the Google APIs system image) if licenses aren't accepted first.#    The system-image arch must match your host: `arm64-v8a` for Apple#    Silicon (M1/M2/M3), `x86_64` for Intel Macs. Check with `uname -m`.yes | sdkmanager --licensessdkmanager --install "platform-tools" "emulator" "system-images;android-34;google_apis;arm64-v8a"

# 1. JDK — required by sdkmanager itself, and by the gradle-* toolsbrew install --cask temurin@17
# 2. cmdline-tools (provides sdkmanager)brew install --cask android-commandlinetools
# 3. Set ANDROID_HOME and create the directory BEFORE running sdkmanager,#    otherwise sdkmanager has no install target.export ANDROID_HOME="$HOME/Library/Android/sdk"mkdir -p "$ANDROID_HOME"
# 4. Accept all SDK licenses first, then install packages.#    `sdkmanager --install` aborts on unaccepted per-package licenses#    (e.g. the Google APIs system image) if licenses aren't accepted first.#    The system-image arch must match your host: `arm64-v8a` for Apple#    Silicon (M1/M2/M3), `x86_64` for Intel Macs. Check with `uname -m`.yes | sdkmanager --licensessdkmanager --install "platform-tools" "emulator" "system-images;android-34;google_apis;arm64-v8a"

Persist ANDROID_HOME and put the SDK binaries on your PATH by appending to ~/.zshrc (or ~/.bashrc):

bash

export ANDROID_HOME="$HOME/Library/Android/sdk"export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/emulator:$PATH"

export ANDROID_HOME="$HOME/Library/Android/sdk"export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/emulator:$PATH"

Installation

After installation, run the built-in diagnostics to verify your environment:

Updating

Setup

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

Claude Code

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

json

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

json

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

{  "mcpServers": {    "replicant": {      "command": "npx",      "args": ["-y", "replicant-mcp"]    }  }}

OpenAI Codex CLI

Add to ~/.codex/config.toml:

Or via CLI:

Note: Ensure adb and emulator are in your PATH, or set ANDROID_HOME environment variable. On macOS: ~/Library/Android/sdk, on Linux: ~/Android/Sdk.

Example

You: "I just changed the checkout flow. Build the app, go through checkout      with a test product, and make sure the confirmation screen shows up."
Claude: [Builds debug APK, installs on emulator, launches app]        [Taps "Electronics" category → "Wireless Headphones" → "Add to Cart"]        [Navigates to cart, taps "Checkout"]        [Fills shipping form, taps "Place Order"]
        Confirmation screen is showing:        - Order #38291        - "Wireless Headphones" × 1        - Total: $79.99        - Estimated delivery: Jan 30
        The flow works. Want me to test the edge cases—empty cart,        invalid address, payment failure?

You: "I just changed the checkout flow. Build the app, go through checkout      with a test product, and make sure the confirmation screen shows up."
Claude: [Builds debug APK, installs on emulator, launches app]        [Taps "Electronics" category → "Wireless Headphones" → "Add to Cart"]        [Navigates to cart, taps "Checkout"]        [Fills shipping form, taps "Place Order"]
        Confirmation screen is showing:        - Order #38291        - "Wireless Headphones" × 1        - Total: $79.99        - Estimated delivery: Jan 30
        The flow works. Want me to test the edge cases—empty cart,        invalid address, payment failure?

Design

replicant-mcp uses progressive disclosure (summaries first, details on demand) to minimize token usage, and accessibility-first UI automation for faster, cheaper, more reliable interactions than screenshot-based approaches. See docs/architecture.md for details.

More Info

Configuration: Set REPLICANT_CONFIG for advanced options. See docs/configuration.md.
Logging: Set REPLICANT_LOG_LEVEL (error, warn, info, debug) and REPLICANT_LOG_FORMAT (json for structured output) to control server logging. Logs are written to stderr.
Troubleshooting: Common issues and solutions in docs/troubleshooting.md.
Tool documentation: Ask Claude to call rtfm with a category like "build", "adb", "emulator", or "ui".

Documentation

Document	Description
Architecture	Design overview and progressive disclosure pattern
Configuration	Config file reference, environment variables, Gradle setup
API Stability	Tool API versioning policy and deprecation process
Security Model	adb-shell safety model, command denylist, threat boundaries
Support Matrix	Tested OS, Node.js, Android SDK, and emulator versions
Known Limitations	Accessibility gaps, timeouts, single-device focus, and more
Artifacts	`.replicant/` directory contents and privacy considerations
Troubleshooting	Common issues and solutions
Changelog	Version history
Security Policy	Vulnerability reporting process
Support / Getting Help	How to report bugs and ask questions
Contributing	Development setup and guidelines

Contributing

See CONTRIBUTING.md for development setup and guidelines.

Acknowledgments

Inspired by xc-mcp for iOS
Built on the Model Context Protocol

License

MIT

Questions? Open an issue

Source: README.md at commit 9d24a45

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.6.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts