A
licenseA
qualityC
maintenanceEnables 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.
33
20 npm
MIT
Specter MCP
by abd3lraouf
Related Servers
Alternatives to Specter MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to build, deploy, drive, and debug Android apps — managing Gradle builds, emulators, adb deployment, logcat capture, and full UI automation.5324 npmMIT
- AlicenseBqualityDmaintenanceTransforms AI assistants into mobile development powerhouses with 36 tools for Flutter, Android, and iOS development, including intelligent device management, automated builds, testing, and deployment workflows.3124 npm7MIT
- AlicenseAqualityBmaintenanceEnables end-to-end generation, scaffolding, testing, diagnosis, and auditing of Kotlin applications for Android, Compose Multiplatform, Ktor, and Spring Boot through a coordinated team of specialized agents.241MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with enterprise-grade access to Kotlin-based Android development projects, including security, privacy compliance, AI-powered code generation, and comprehensive development tools.AGPL 3.0
- AlicenseBqualityDmaintenanceEnables AI agents to inspect, log, and control React Native apps on Android emulators or iOS simulators, including UI tree, tap, scroll, and hot reload.22989 npm5MIT
TDQS
A3.7/5.0
Scored across 15 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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
ActivityInactive
ResponsivenessNo issues