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
Server capabilities have not been inspected yet.
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
The three tools have mostly distinct purposes: building, running tests, and running instrumented tests. However, 'test' and 'instrumentedTest' could be slightly ambiguous as instrumented tests are a subset of tests, but the descriptions clarify this distinction.
All tool names follow a consistent snake_case pattern with clear, descriptive verbs ('build', 'test', 'instrumentedTest'). There are no deviations in naming conventions, making the set predictable and readable.
With only 3 tools, the server feels thin for an Android project domain, which typically involves more operations like linting, debugging, or emulator management. While the tools cover core build and test workflows, the scope seems limited.
The tool surface is significantly incomplete for Android development. It lacks essential operations such as cleaning, linting, deploying, debugging, or managing dependencies, which are common in this domain and could lead to agent failures in broader tasks.