Android Project MCP Server
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buildB | Build the Android project in the folder |
| testC | Run test for the Android project in the folder |
| instrumentedTestB | Run instrumented test for the Android project in the folder |
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 3 tools
Build is clearly distinct from testing, but 'instrumentedTest' and 'test' are ambiguous: the names are too similar and descriptions lack differentiation, potentially causing confusion.
Naming is inconsistent: 'build' and 'test' are lowercase, while 'instrumentedTest' uses camelCase. No clear verb_noun pattern.
Only 3 tools for an Android project is minimal. Common tasks like linting, cleaning, or building variants are missing, making the surface feel thin.
The tool surface lacks essential Android build operations (e.g., clean, lint, assembleDebug, generate signed APK). Testing coverage is incomplete without specifying unit vs integration.