Version-aware mobile docs MCP server for Android (Jetpack/Compose) and Apple (SwiftUI/UIKit)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mobile-docs-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mobile-docs-mcp [](https://pypi.org/project/mobile-docs-mcp/) [](https://pypi.org/project/mobile-docs-mcp/) [](LICENSE) A version-aware documentation MCP server for mobile development — the context7 idea, but specialized for the thing generic doc proxies get wrong: **which version of an API you can actually use.** > **Install:** `uvx mobile-docs-mcp` (nothing to clone) — or `pip install > mobile-docs-mcp`. Published on [PyPI](https://pypi.org/project/mobile-docs-mcp/). > Jump to [Editor & IDE setup](#editor--ide-setup-ios--android). It indexes Android (Jetpack / androidx / Compose) and Apple (SwiftUI / UIKit) documentation with `since` / `deprecated` / `removed` metadata on every symbol, so an agent can *verify an API exists on the version the project targets* before writing code against it. ## Why it's different from a doc proxy Most "Apple docs" / "Android docs" MCP servers live-fetch and parse the current doc site. They answer "what is `scrollTargetBehavior`?" but not "can I use it on iOS 16?" — and that second question is where coding agents hallucinate. Every result here is filtered and annotated against a target version. ## Tools | Tool | Purpose | |------|---------| | `search_mobile_docs` | Hybrid (BM25 + optional vector) retrieval, filtered by platform + target version | | `get_api_reference` | Full symbol card: signature, availability, deprecation/migration pointer | | `verify_api_exists` | Anti-hallucination check — real AND usable on a given version? | | `list_api_versions` | since / deprecated / removed timeline + migration lineage | | `get_release_notes` | What changed in a library/version | Example verdict: ``` verify_api_exists("scrollTargetBehavior", "16.0", "apple") → ❌ NOT AVAILABLE — introduced in 17.0, newer than 16.0. Will not compile there.…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.