replicant-mcp

io.github.thecombatwombat由 GitHub 账号 thecombatwombat 发布v1.6.7更新于 Oct 24, 2026

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

已验证STDIO仅桌面浏览器自动化开发者工具

概览

AI 生成的概览

让 AI 助手在模拟器或已连接设备上构建、测试、安装并操作 Android 应用。

可以做什么
这是一个 Android 开发用 MCP 服务器,可构建 APK 与 bundle、运行单元测试和仪器化测试,并管理模拟器(创建、启动、停止、清除数据、快照)。它能安装、启动应用并清除应用数据,按包名、标签、级别和时间过滤 logcat,还提供以无障碍树优先的 UI 自动化,例如按文本查找元素、点击、输入文本和截图。此外可做环境健康检查,并通过渐进式披露控制 token 消耗。
适用场景
适合让助手直接在 Android 项目中工作:编译与测试构建、在模拟器或设备上复现 UI 流程、查看过滤后的日志、排查崩溃,而无需复制粘贴命令输出。最适合已经配置好 Android 工具链的开发者。
运行要求
通过 npx 在本地运行,需要 Node.js 18+。需要 Android SDK,且 adb 与 emulator 在 PATH 中,或设置 ANDROID_HOME;构建工具需要带 gradlew 的项目。可选环境变量 REPLICANT_CONFIG、REPLICANT_LOG_LEVEL、REPLICANT_LOG_FORMAT 用于配置与日志。仅支持桌面端。
安装前请注意
该服务器会操作真实设备与模拟器:安装和卸载应用、清除应用数据、清除模拟器数据,并发送点击与文本输入,因此可能更改或删除目标设备上的状态。它会在 .replicant 目录写入产物,文档提示需注意隐私问题。未声明任何凭据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 replicant-mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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-mcpWith replicant-mcp
"Run ./gradlew assembleDebug, then adb install, then adb shell am start...""Build and run the app"
Copy-paste logcat output, lose contextAI reads filtered logs directly
Screenshot → describe UI → guess coordinatesAI sees accessibility tree, taps elements by text
5,000 tokens of raw Gradle output50-token summary + details on demand

Features

CategoryCapabilities
Build & TestBuild APKs/bundles, run unit and instrumented tests, list modules/variants/tasks, test regression detection with baseline comparison
EmulatorCreate, start, stop, wipe emulators; save/load/delete snapshots
Device ControlList connected devices, select active device, query device properties
App ManagementInstall, uninstall, launch, stop apps; clear app data
Log AnalysisFilter logcat by package, tag, level, time
UI AutomationAccessibility-first element finding, spatial proximity search, tap, text input, screenshots
DiagnosticsEnvironment 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
Installing prerequisites (macOS via Homebrew)

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

Node.js 18+

bash
brew install node

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

bash
brew install --cask android-platform-tools

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"

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"

Installation

bash
npm install -g replicant-mcp

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

bash
replicant doctor

Updating

bash
npm update -g replicant-mcp

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"]    }  }}

Claude Code

bash
claude mcp add replicant -- npx -y replicant-mcp

Cursor

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

json
{  "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"]    }  }}

OpenAI Codex CLI

Add to ~/.codex/config.toml:

toml
[mcp_servers.replicant]command = "npx"args = ["-y", "replicant-mcp"]

Or via CLI:

bash
codex mcp add replicant -- npx -y replicant-mcp

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?

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

DocumentDescription
ArchitectureDesign overview and progressive disclosure pattern
ConfigurationConfig file reference, environment variables, Gradle setup
API StabilityTool API versioning policy and deprecation process
Security Modeladb-shell safety model, command denylist, threat boundaries
Support MatrixTested OS, Node.js, Android SDK, and emulator versions
Known LimitationsAccessibility gaps, timeouts, single-device focus, and more
Artifacts.replicant/ directory contents and privacy considerations
TroubleshootingCommon issues and solutions
ChangelogVersion history
Security PolicyVulnerability reporting process
Support / Getting HelpHow to report bugs and ask questions
ContributingDevelopment setup and guidelines

Contributing

See CONTRIBUTING.md for development setup and guidelines.


Acknowledgments


License

MIT


Questions? Open an issue

来源:README.md,提交 9d24a45

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.6.7最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分