summarize_vhalLABSCO SUMMARY
It checks whether Android already has the property before helping you define a new one.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Deciding whether you need a new property at all
Validate the request against the current Android release first; if something close exists, you get it back with a similarity score.
02
Working out what to implement first
Discover the properties related to the one you care about and get a suggested order for implementing them.
03
Reading the actual implementation of a property
Find it in Android source, then get the source-level analysis with usage patterns and dependencies.
04
Getting the change ready to submit
Generate the HAL definitions, APIs, tests and build files, then a pull-request description with a review checklist.
8 tools
Listed in project docs. Your client may show a different list.
lookup_android_source_codediscover_related_propertiesanalyze_vhal_implementationgenerate_vhal_implementation_codegenerate_vhal_pr_messagevalidate_vhal_sources_and_enhance_summaryvalidate_vhal_property_requestBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
Python 3.12 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/feevlic/vhal-mcp-server.git
cd vhal-mcp-server
pip install -e .MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"vhal-mcp-server": {
"command": "/Users/<YOUR_USERNAME>/.local/bin/uv",
"args": [
"run",
"--directory",
"/Users/<YOUR_USERNAME>/vhal-mcp-server",
"python",
"main.py"
],
"env": {
"PYTHONPATH": "/Users/<YOUR_USERNAME>/vhal-mcp-server"
}
}
}
}The [] in these paths is your own username (the README's example is /Users/yourusername/.local/bin/uv). /Users/[]/.local/bin/uv is the output of which uv, and both /Users/[]/vhal-mcp-server values the absolute path of your clone. Full paths are needed because Claude Desktop may not see your shell's PATH.
