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、執行單元測試與 instrumentation 測試,並管理模擬器(建立、啟動、停止、清除資料、快照)。它能安裝、啟動應用程式並清除應用程式資料,依套件、標籤、等級與時間篩選 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 分