mobile-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mobile_docsA | Search Android (Jetpack/androidx/Compose) and Apple (SwiftUI/UIKit) docs. Args: query: what you're looking for, e.g. "animate lazy list item". platform: "android" | "apple" | "" for both. target_version: version the project targets (e.g. "1.6.0" for androidx, "16.0" for iOS). Results the target can't use are filtered out unless include_unavailable is true, and each hit is annotated with its availability status for that version. include_unavailable: keep results not yet available at target_version. limit: max results. |
| get_api_referenceB | Full reference card for a symbol: signature, summary, availability, and any deprecation/migration pointer. Use exact names ("NavigationStack", "animateItem") for best results. |
| verify_api_existsA | Anti-hallucination check. Confirms whether an API is real AND usable on a specific version before an agent writes code against it. Args: name: symbol name, e.g. "scrollTargetBehavior" or "animateItem". target_version: the version to check against ("17.0", "1.6.0", "34"). platform: "android" | "apple" | "" to search both. Returns a verdict: available / deprecated / not-yet-available / unknown, with the migration target when relevant. |
| list_api_versionsB | Show the availability timeline (since / deprecated / removed) for a symbol and its migration lineage. |
| get_release_notesA | Retrieve release-note chunks describing what changed. Good for "what's new in Compose 1.7" or "SwiftUI iOS 17 changes". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a unique and clearly defined purpose: get_api_reference for symbol details, get_release_notes for release information, list_api_versions for availability timelines, search_mobile_docs for general search, and verify_api_exists for existence checks. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., get_api_reference, search_mobile_docs), making the set predictable and easy to understand.
With 5 tools covering the key operations for mobile documentation (search, reference, release notes, availability, verification), the count is well-scoped and appropriate for the domain.
The tool set provides comprehensive coverage for mobile API documentation: searching, getting detailed references, checking availability across versions, reviewing release notes, and verifying existence. No obvious gaps for typical developer workflows.