Android Project MCP Server
# Android Project MCP Server
A Model Context Protocol server that builds Android project that enables seamless workflow working with Android projects in Visual Studio Code using extensions like Cline or Roo Code.
<a href="https://glama.ai/mcp/servers/@ShenghaiWang/androidbuild">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ShenghaiWang/androidbuild/badge" alt="Android Project Server MCP server" />
</a>
### Available Tools
- `build` - Build Android project
- `folder` (string, required): The full path of the current folder that the Android project sits
- `test` - Run unit test
- `folder` (string, required): The full path of the current folder that the Android project sits
- `instrumentedTest` - Run Instrumented test
- `folder` (string, required): The full path of the current folder that the Android project sits
## Installation
### Using uv (recommended)
When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will
use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *mcpandroidbuild*.
### Using PIP
Alternatively you can install `mcpandroidbuild` via pip:
```
pip install mcpandroidbuild
```
After installation, you can run it as a script using:
```
python -m mcpandroidbuild
```
## Configuration
### Configure for Claude.app
Add to your Claude settings:
<details>
<summary>Using uvx</summary>
```json
"mcpServers": {
"mcpandroidbuild": {
"command": "uvx",
"args": ["mcpandroidbuild"]
}
}
```
</details>
<details>
<summary>Using pip installation</summary>
```json
"mcpServers": {
"mcpandroidbuild": {
"command": "python",
"args": ["-m", "mcpandroidbuild"]
}
}
```
</details>
## License
mcpandroidbuild MCP tool is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.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.