AndroJack MCP

In 2025, theStack Overflow Developer Surveyasked 49,000 developers about their experience with AI coding tools. The results should alarm every Android engineer:

- 84% of developersnow use AI coding tools — up from 76% the year before.
- Trust in AI accuracy collapsedfrom 40% to just29%in a single year.
- 35% of all Stack Overflow visits in 2025are now triggered by developers debugging and fixing AI-generated code.

The gap between usage and trust is not a coincidence. It is the product of a structural problem:AI models predict tokens, not APIs.They were trained on a snapshot of the world and have no mechanism to know what changed at API 30, what shipped at Google I/O 2025, or what Google Play now rejects at review time.

For Android developers, this failure mode is uniquely dangerous. Android has the fastest-moving ecosystem in mobile development — a new Compose BOM every month, Navigation 3 going stable after seven years of Nav2, Android 16 rewriting the rules on screen orientation locking — and most AI tools have training data that is six months to two years stale by the time you use them.

The result is not just bad code. It isconfidently bad code.

⚡ What Actually Breaks In Practice — Documented Evidence

These are not hypothetical risks. They are documented failure modes from real developer projects.

The Navigation 3 Hallucination (January 2026)

A published case study fromAtomic Robotdocumented a live Navigation 2 → Navigation 3 migration using both Gemini and Claude — with internet access enabled on both. The conclusion, verbatim:

"LLMs still hallucinate versions. Even with internet access, both agents wanted to use an outdated release candidate instead of the stable 1.0.0 release."

Navigation 3 went stable in November 2025 after seven years of the same library. It is a complete architectural rethink: back stacks are now plain Kotlin lists, the monolithic nav graph is gone, andNavDisplayreplacesNavController. Google's own migration guide is so aware that AI tools get this wrong that it now contains special"AI Agent:" annotations— instructions embedded directly in the official docs for AI tools to follow. An AI tool that generates Nav2 code for a new Compose project in 2026 is not making a small mistake. It is creating an architectural incoherence that requires a full rewrite to fix.

Jetpack Compose ships a new BOM every month. Since most models' training cutoffs, these APIs changed:

Every one of these compiles. Most run without errors. The bugs surface later in CI flakiness, UI regressions, or Play Store review failures.

The Android 16 / API 36 Mandate (August 2026 deadline)

Android 16 made a platform-level change affecting every published app: on devices ≥600dp — tablets, foldables, ChromeOS — apps canno longer lock screen orientationor restrict resizability. Google Play requires API 36 targeting by August 2026.

An AI tool generatingandroid:screenOrientation="portrait"orandroid:resizeableActivity="false"today is generating code that will trigger App Compatibility warnings in Play Console, fail large-screen quality checks, and get apps demoted in Play Store search results.

The business impact is not theoretical:Foldable users spend 14× more on appsthan phone-only users. Tablet + phone users spend 9× more. FlipaClip saw 54% growth in tablet users within four months of going adaptive.

Kotlin Multiplatform went mainstream in 2025 — over 900 new KMP libraries published, Room added KMP support, companies now hire specifically for KMP skills. When a developer on a KMP project asks an AI tool to add database support, the AI generates Android-only Room code. It compiles. It runs perfectly on Android.The iOS build fails.The developer spends hours debugging before realizing the root cause: their AI tool does not know KMP exists.

AndroJack is adocumentation-grounded Android engineering MCP server. It gives your AI coding assistant23 specialized toolsthat fetch live, verified answers from official Android and Kotlin sources — instead of predicting from stale training data.

It does not make the AI smarter. It makes the AIaccountable to evidence.

Think of it as a pre-build linter for LLMs. While other tools retrieve documentation, AndroJack acts as a strict architectural gatekeeper.

Without AndroJack: You ask → AI predicts from stale weights → Code (possibly wrong) With AndroJack: You ask → AI calls tool → Tool fetches official source live → AI reads verified answer → Code (grounded)

Every example keeps AndroJack local by default and runs the published package vianpx -y androjack-mcp@2.0.0.

📍 The Ecosystem: AndroJack vs. Other MCPs

Android Skills and AndroJack solve different halves of the same problem. Skills give an agent contextbeforeit writes code. AndroJack'sandroid_code_validatoris the gate that runsafter— checking the generated code against 28 rules before you ever see it. Use both if your agent supports Agent Skills.

v2.0.0 — Security Hardening, Compose-First, Developer Verification

- Content sanitizer for indirect prompt injection—src/content-sanitizer.tsneutralizes structural injection patterns (fake role markers, instruction-reset framing) in any externally-fetched text before it reaches the calling agent's context.android_debuggerresults fromissuetracker.google.com— the only allowlisted domain indexing free-text, user-submitted content — are wrapped in an explicit untrusted-data boundary.
- Dependency vulnerabilities patched— resolved 7 vulnerabilities (3 high) in transitiveundici/qsvia acheerioupdate. Zero breaking changes, 0 vulnerabilities in the shipped tree.
- Tool 23:android_developer_verification— Google's developer verification program enforces from September 30, 2026 (Brazil, Indonesia, Singapore, Thailand first; global 2027). Covers registration paths, timeline, enterprise exemptions, and CI/CD bulk-registration APIs.
- Compose-First platform shift reflected— as of May 19, 2026, Android UI development is officially Compose First; View-based patterns (Fragments, RecyclerView, ViewPager) are flagged as maintenance-mode wherever queried, sourced directly from Google's own announcement rather than left silently outdated.
- Compose 1.11 v2 Testing Framework— full migration guide for the new defaultStandardTestDispatcherbehavior, plus a validator rule (UNCONFINED_DISPATCHER_COMPOSE_TEST) that flags the old assumption.
- Navigation 3 Scene Decorators (1.1)— persistent chrome (bottom bars, rails, dialogs) without per-screen awareness.
- Android Studio codename corrected— was two full codenames stale ("Panda 2"). Now correctly reflectsQuail (2026.1.x)as current stable, AGP 9.2.0.
- Android Skills positioning— documents Google's first-party Android Skills/CLI (April 2026) and positions AndroJack's validator as the complementary post-generation enforcement gate, not a competing retrieval layer.
- 28 validator rules(was 26) — addedUNCONFINED_DISPATCHER_COMPOSE_TESTandNEW_FRAGMENT_CLASS_COMPOSE_FIRST.
- Fabricated version numbers removed— a prior session's dependency version catalog example asserted several unverified version numbers. Replaced with only-confirmed values plus explicitCHECK_LIVE_VIA_gradle_dependency_checkerplaceholders.
- Full version sync— closed a gap wheresrc/version.tshad been bumped without propagating topackage.json, all IDE config files, and manifest files — now enforced as a release checklist item.

v1.7.1 — Engineering Hardening & Community Parity

- 54-Test Coverage— Implemented comprehensive unit and contract tests for validator rules, HTML parser, LRU cache, and HTTP security layer.
- Discovery Parity— Fixed/.well-known/mcpendpoint to correctly reporttools: 22.
- Dependency Sanitization— Removednode-fetch(migrated to nativefetch) and pruned stale overrides for a cleaner supply chain.
- Rule Hardening— Improved Compose component detection forNavHostandBottomAppBar.
- URL Remediation— Fixed broken documentation anchors for Android 17ACCESS_LOCAL_NETWORKandhandoff.

- Tool 22:android_api17_compliance— Full reference for Android 17 platform stability (March 26, 2026).
- 31 validator rules— Expanded from 24 to 31 with dedicated Android 17 and Room 3.0 removal checks.
- WindowManager 1.5.0— Added Large (1200dp) and Extra-large (1600dp) breakpoints and layout patterns.
- Room 3.0 alpha— Support for modern SQLiteDriver migration paths.

Built because 35% of Stack Overflow visits in 2025 are developers debugging AI-generated code.
AndroJack exists so none of those visits are yours.

Generat 22 types mermaid architecture diagrams with natural language description

Access and analyze Overleaf projects and LaTeX files through Git integration.

Allows AI assistants to interact with the GitHub API for repository management, code collaboration, and other development tasks.

iOS simulator automation MCP server — build, test, screenshot (20ms), UI interaction, logging, git. Direct WDA integration, no Appium overhead. 55 tools, Free + Pro tier.

Self-hosted MCP server over your markdown notes: hybrid search and note reading with sourced answers. The same vault is also a website, so the agent's memory is readable, git-diffable markdown. Single Go binary + SQLite, MIT.

Debug and drive live React Native apps: logs, network, screenshots, UI automation, and fiber-tree inspection.

Secure MCP access to local repositories from ChatgptWeb without shell, Git, or arbitrary writes.

Python MCP server for TMDB search, Stremio library management, and Android TV playback/control over native ADB.

Creates commit messages from staged files in a local git repository.