AndroJack-mcp
Related Servers
Alternatives to AndroJack-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides AI coding assistants with access to Google's Android development skills library through an MCP server. Enables developers to discover, search, and apply Android best practices directly within their coding environment without manual copying.223-
- AlicenseBqualityCmaintenanceProvides on-demand access to AOSP and Jetpack source code to help AI understand Android framework internals. It features a hybrid architecture using Tree-sitter and LSP for precise code extraction, cross-file navigation, and local source indexing.11100Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with live, searchable documentation for any programming library, eliminating hallucinated APIs by returning current, structured API references.-
- AlicenseAqualityDmaintenanceProvides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.542 npm36MIT
- AlicenseAqualityCmaintenanceIt enables AI engineers to retrieve real-time official documentation for 45+ libraries, search across frameworks, and extract code examples directly inside MCP-compatible assistants, eliminating stale training data and outdated API usage.5MIT
- AlicenseCqualityCmaintenanceProvides real-time access to up-to-date library documentation and code examples for any programming library. Helps AI coding assistants deliver accurate, current information instead of relying on outdated training data.16 npmMIT
TDQS
Scored across 22 tools
Most tools target clearly distinct subdomains like permissions, testing, navigation, and dependencies, making selection straightforward. A few potential confusions exist: android_api36_compliance vs android_api17_compliance use different numbering schemes (API level vs Android version), and android_official_search could overlap with any specific reference tool.
The majority follow an android_<topic>_<role> pattern, but there are notable exceptions: architecture_reference, gradle_dependency_checker, kotlin_best_practices, and material3_expressive break the android_ prefix. Naming also mixes version-based identifiers (api17) with API-level identifiers (api36), creating inconsistency.
At 22 tools, the set lands in the 16-25 range that feels heavy. While each tool covers a distinct Android topic, many are structurally identical 'reference' lookups that could potentially be consolidated into fewer topic-routed tools. The breadth is justifiable but borderline.
The tool surface is exceptionally comprehensive for Android/Kotlin development, spanning search, API status, dependencies, architecture, debugging, testing, build/publish, compliance, KMP, XR, Wear OS, on-device AI, and Play policy. The android_code_validator loop-back closes the generation-validation cycle, leaving no obvious dead ends.