That check is the useful part — defining a vendor property that duplicates a standard one is expensive to undo later. The validation tool also scores its own confidence and flags documentation links that no longer resolve, rather than quoting a dead page.
A server for Android Automotive developers working on the Vehicle Hardware Abstraction Layer. It searches Android source for vHAL properties, explains how they relate, and generates the files a new property needs.
- lookup_android_source_code — find vHAL properties with their IDs, categories and links to the source
- analyze_vhal_implementation — the source-level detail for one property, with usage patterns and dependencies
- discover_related_properties — what a property depends on and a suggested implementation order
- summarize_vhal — answers to a specific vHAL question drawn from the automotive documentation
- validate_vhal_sources_and_enhance_summary — the same, with URL accessibility checked, confidence scoring and clear citations
- validate_vhal_property_request — check whether the property already exists in Android before you invent one, and get a correctly named vendor property when it does not
- generate_vhal_implementation_code — HAL definitions, Java APIs, tests and build configuration for a new property
- generate_vhal_pr_message — a structured pull-request description with the technical detail and a review checklist
Python 3.12 or higher and an internet connection, since it reads live documentation. Installed with pip install -e . and run through uv; the package is vhal-mcp-server. No credentials.
Build from source — clone the repository and build it, then point your client at the binary
