Specter MCP
Enables building, testing, debugging, and automating Android applications with tools for device management, UI interaction, crash analysis, app state inspection, and deep linking
Provides build automation for Android projects through Gradle build system integration
Enables building, testing, debugging, and automating iOS applications with tools for simulator management, UI interaction, crash symbolication, app state inspection, and deep linking
Provides build automation and tooling for iOS projects through Xcode command line tools and xcodebuild
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Specter MCP build my Android app in debug mode and install it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What is Specter MCP?
Specter MCP enables AI agents (Claude, GPT, etc.) to build, test, debug, and interact with Android and iOS applications through the Model Context Protocol. Think of it as giving your AI assistant the ability to:
Build and deploy your mobile apps
Take screenshots and interact with UI elements
Run unit tests and E2E tests (Maestro)
Analyze crash logs and debug issues
Inspect app state (preferences, databases, logs)
Related MCP server: devilge
Prerequisites
Requirement | Version | Verify Command |
Node.js | 20+ |
|
Android SDK | Any |
|
Xcode CLI (macOS) | Any |
|
Maestro (optional) | Any |
|
Quick Setup
# Android SDK (if not installed via Android Studio)
export ANDROID_SDK_ROOT="$HOME/Library/Android/sdk"
export PATH="$PATH:$ANDROID_SDK_ROOT/platform-tools"
# iOS (macOS only)
xcode-select --install
sudo xcodebuild -license accept
# Maestro (optional, for E2E testing)
curl -Ls "https://get.maestro.mobile.dev" | bashInstallation
Option 1: npm (Recommended)
npm install -g specter-mcpOption 2: From Source
git clone https://github.com/abd3lraouf/specter-mcp.git
cd specter-mcp
npm install && npm run buildConfiguration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"specter-mcp": {
"command": "specter-mcp"
}
}
}Claude Code
Add to your project's .mcp.json:
{
"mcpServers": {
"specter-mcp": {
"command": "specter-mcp"
}
}
}With Environment Variables
{
"mcpServers": {
"specter-mcp": {
"command": "specter-mcp",
"env": {
"SPECTER_DEBUG": "true",
"ANDROID_SDK_ROOT": "/path/to/android/sdk"
}
}
}
}From Source
{
"mcpServers": {
"specter-mcp": {
"command": "node",
"args": ["/absolute/path/to/specter-mcp/dist/index.js"]
}
}
}Available Tools (15)
Category | Tool | Description |
Build |
| Build Android/iOS app (debug/release) |
| Install APK or .app on device | |
| Launch installed app | |
UI |
| Screenshot + UI hierarchy |
| Tap, swipe, input text | |
Testing |
| Run unit tests |
| Run Maestro E2E flows | |
| Detekt, SwiftLint, ktlint | |
Environment |
| List emulators/simulators |
| Boot/shutdown devices | |
| Clean build caches | |
Debug |
| Parse crash logs, symbolicate |
| Filter device logs | |
| Read prefs, databases | |
Navigation |
| Open deep links |
Usage Examples
Build & Deploy
You: Build my Android app in debug mode and install it
Claude: I'll build and deploy your app.
→ build_app(platform: "android", variant: "debug")
→ install_app(platform: "android", appPath: "...")
→ launch_app(platform: "android", appId: "com.example.app")Debug a Crash
You: My iOS app crashed, help me debug it
Claude: Let me analyze the crash.
→ analyze_crash(platform: "ios", appId: "com.example.app")
→ inspect_logs(platform: "ios", minLevel: "error")UI Testing
You: Take a screenshot and tap the login button
Claude: I'll capture the UI and interact with it.
→ get_ui_context(platform: "android")
→ interact_with_ui(platform: "android", action: "tap", element: "Login")Run E2E Tests
You: Run my login flow test on both platforms
Claude: Running Maestro flows.
→ run_maestro_flow(platform: "android", flowPath: "./maestro/login.yaml")
→ run_maestro_flow(platform: "ios", flowPath: "./maestro/login.yaml")Environment Variables
Variable | Default | Description |
|
| Enable debug logging |
|
| Log level (error/warn/info/debug) |
|
| Default timeout (ms) |
| auto | Android SDK path |
| - | Default Android device |
|
| Default iOS simulator |
Troubleshooting
"adb: command not found"
export PATH="$PATH:$ANDROID_SDK_ROOT/platform-tools""No devices found"
# Android: Start emulator
emulator -avd Pixel_6_API_34
# iOS: Boot simulator
xcrun simctl boot "iPhone 15 Pro""xcrun: error: unable to find utility"
xcode-select --installDebug Mode
{
"env": {
"SPECTER_DEBUG": "true",
"SPECTER_LOG_LEVEL": "debug"
}
}Project Structure
src/
├── index.ts # MCP server entry
├── config.ts # Configuration
├── platforms/ # Android/iOS utilities
│ ├── android/ # ADB, Gradle, logcat
│ └── ios/ # simctl, xcodebuild, crash parsing
├── tools/ # MCP tool implementations
│ ├── build/ # build_app, install_app, launch_app
│ ├── ui/ # get_ui_context, interact_with_ui
│ ├── testing/ # run_unit_tests, run_maestro_flow, run_linter
│ ├── environment/ # list_devices, manage_env, clean_project
│ ├── crash/ # analyze_crash
│ ├── navigation/ # deep_link_navigate
│ └── observability/ # inspect_logs, inspect_app_state
└── utils/ # Shell, image processing, XML parsingDevelopment
npm install # Install dependencies
npm run build # Build TypeScript
npm test # Run tests (695 tests)
npm run test:coverage # Coverage report
npm run lint # ESLint
npm run typecheck # Type checkDocumentation
API Reference — All 15 tools with parameters
Configuration Guide — Environment variables & setup
Getting Started — First steps
License
MIT © Specter MCP Contributors
Available Tools
15 toolsanalyze_crashA
Analyze crash logs and device logs to identify crash patterns and root causes. Supports both Android (logcat) and iOS (crash files + oslog). For live device analysis, checks device logs automatically. For iOS, can also analyze .ips/.crash files with symbolication.
Inputs: platform (required), appId, deviceId, crashLogPath, +4 more.
build_appB
Build a KMM application for Android or iOS. Returns structured build result with error details on failure.
Inputs: platform (required), variant, clean, iosDestination, +3 more.
clean_projectA
Clean project build caches, DerivedData, and other temporary files. Helps resolve build issues caused by stale caches.
Inputs: projectPath (required), cleanGradle, cleanDerivedData, cleanBuild, +3 more.
get_ui_contextB
Capture the current UI state including screenshot and interactive elements. Returns a compressed screenshot and a list of UI elements with their properties.
Inputs: platform (required), deviceId, includeAllElements, maxDepth, +3 more.
inspect_app_stateA
Inspect app preferences (SharedPreferences/UserDefaults) and SQLite databases. Can list all preferences, inspect specific databases, or run SQL queries.
Inputs: appId (required), platform (required), deviceId, includePreferences, +6 more.
inspect_logsA
Inspect device logs (Android logcat or iOS unified logs). Can filter by app, log level, tags, patterns, and time range.
Inputs: platform (required), appId, deviceId, minLevel, +11 more.
install_appB
Install an app on a device or simulator. For Android, installs an APK. For iOS, installs an .app bundle.
Inputs: platform (required), appPath (required), deviceId.
interact_with_uiA
Perform UI interactions like tap, swipe, or text input. Can target elements by ID/text or by coordinates.
Inputs: platform (required), action (required), element, x, +5 more.
launch_appB
Launch an installed app on a device or simulator.
Inputs: platform (required), appId (required), deviceId, clearData, +1 more.
list_devicesB
List available devices (emulators, simulators, physical devices). Returns device details including status and platform.
Inputs: platform, status, includeAvds, includeUnavailable.
manage_envB
Manage device environment: boot, shutdown, or restart emulators and simulators.
Inputs: action (required), platform (required), deviceId, waitForReady, +1 more.
run_linterA
Run code linter (Detekt, Android Lint, SwiftLint, ktlint). Returns structured lint results with issue locations and suggestions.
Inputs: platform (required), projectPath (required), linter, module, +3 more.
run_maestro_flowA
Run a Maestro E2E test flow. Returns structured results with step-by-step status. On failure, generates a failure bundle with screenshot and logs for debugging.
Inputs: flowPath (required), platform (required), deviceId, appId, +3 more.
run_unit_testsB
Run unit tests for Android or iOS. Returns structured test results with pass/fail status and failure details.
Inputs: platform (required), projectPath (required), sourceSet, testClass, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Each tool targets a distinct function: crash analysis, building, cleaning, deep link navigation, UI capture, app state inspection, log inspection, installation, UI interaction, launch, device listing, environment management, linter, E2E tests, and unit tests. There is no ambiguity between tools.
Most tools follow a verb_noun pattern (e.g., analyze_crash, build_app). One exception is deep_link_navigate (noun_verb), and interact_with_ui uses a preposition, but overall the naming is mostly consistent.
15 tools is well-scoped for a mobile app development and testing server. Each tool earns its place, covering build, test, deploy, device management, and analysis without being overwhelming.
The tool set covers core workflows: building, testing (unit, lint, E2E), installing, launching, UI interaction, logging, crash analysis, and device management. Minor gaps like uninstall or app data reset are absent but not critical.
Maintenance
Related MCP Connectors
Investigate iOS and Android crashes and failed UI tests from your coding agent.
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to build, deploy, drive, and debug Android apps — managing Gradle builds, emulators, adb deployment, logcat capture, and full UI automation.5377 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to build, drive, and observe Android/KMM apps end-to-end through ADB and Gradle, with tools for UI automation, error capture, and testing.3343 npmMIT
- AlicenseAqualityCmaintenanceEnables coding agents to build, drive, and debug Android apps on a real device, with screenshots, UI dumps, local vision model analysis, and lock-safe Gradle builds.21MIT
- AlicenseBqualityBmaintenanceEnables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.184MIT