Android Source Explorer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANDROID_SOURCE_LSP | No | Set to 'true' to enable LSP features (cross-file navigation, references, and type information) leveraging Eclipse JDT LS and Kotlin Language Server. |
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_classesB | Search for classes by glob pattern or substring (e.g. 'ViewModel' or 'Activity'). |
| lookup_classB | Retrieve the full source code for a given Android Framework or AndroidX class. |
| lookup_methodB | Look up a specific method's source code within a class. |
| list_class_membersB | List all method and field signatures for a given class. |
| search_in_sourceB | Search for a text/regex pattern within a specific class or across all synced files (if class_name is omitted). |
| list_available_versionsC | List available versions for an AndroidX artifact (e.g. 'androidx.compose.runtime:runtime'). |
| get_class_hierarchyB | Get the inheritance hierarchy (superclass and interfaces) for a class. |
| check_integrityB | Check the integrity of the local source cache and index. |
| goto_definitionB | Resolve the definition of a symbol at a specific position (Requires LSP). |
| find_referencesC | Find all references to a symbol at a specific position (Requires LSP). |
| get_type_infoC | Get type information and documentation (hover) for a symbol (Requires LSP). |
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 11 tools
Most tools have distinct purposes, but there is some overlap between 'lookup_class' and 'lookup_method' as both retrieve source code, which could cause mild confusion. The LSP-based tools ('find_references', 'get_type_info', 'goto_definition') are clearly differentiated, and other tools like 'search_classes' and 'search_in_source' serve unique functions.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'list_available_versions', 'get_class_hierarchy', 'search_classes'). There are no deviations in naming conventions, making the set predictable and easy to understand.
With 11 tools, the count is well-scoped for exploring Android source code, covering tasks from integrity checks to LSP operations and searches. Each tool appears to serve a specific, necessary function without bloat or redundancy, fitting the server's purpose effectively.
The toolset provides comprehensive coverage for source exploration, including search, lookup, LSP features, and version management. A minor gap exists in update or modification tools (e.g., no 'edit_source' or 'apply_patch'), but this is reasonable for a read-only explorer, and agents can work around it.