home / mcp / android development mcp server
Provides Android development guidance, architecture references, and tooling for Android projects via MCP.
Configuration
View docs{
"mcpServers": {
"dpconde-android-dev-mcp": {
"url": "http://localhost:3000/sse",
"headers": {
"PORT": "3000",
"NODE_ENV": "production",
"MCP_TRANSPORT": "sse"
}
}
}
}This MCP server provides Android development assistance through a modular set of tooling and patterns, enabling you to query architecture guidance, UI patterns, module generation, and more from any MCP-compatible AI tool. It exposes a streaming interface for interactive conversations and practical code generation, so you can plan, scaffold, and verify Android projects efficiently.
Connect your MCP client to the SSE endpoint at the URL below to start interacting with the Android development MCP server. You can ask for architecture guidance, generate feature modules, build UI patterns, and search documentation across the available tools.
Typical usage patterns include asking for a recommended Android app architecture, generating a complete feature module (for example a user-profile module with a specific package name), requesting a repository setup for offline-first data handling, or querying the guidance on navigation and testing patterns. You can also request quick references or full architecture documentation to align with NowInAndroid practices.
To connect from Claude or another MCP-enabled AI client, configure the transport to SSE and point it at the serverβs SSE endpoint. Once connected, you can issue natural language requests and receive structured responses that you can adapt directly into your project.
Prerequisites: ensure you have Node.js and npm installed on your system.
Option A: Docker (recommended for quick setup)
# Build and run with Docker Compose
docker-compose up -d
# Or build and run manually
docker build -t android-dev-mcp .
docker run -d -p 3000:3000 --name android-mcp android-dev-mcpThe server will be available at the following endpoints once running.
SSE endpoint: http://localhost:3000/sse
Health check: http://localhost:3000/health
Option B: Local development (no Docker required)
# Install dependencies
npm install
# Build the project
npm run build
# Run in SSE mode (network access)
npm start -- --sse
# Or run in stdio mode (local CLI)
npm startYou can configure your MCP clients to connect via SSE with the following example settings. Ensure the transport is set to SSE and the URL points to the server SSE endpoint.
Claude Desktop configuration example:
{
"mcpServers": {
"android_dev": {
"transport": "sse",
"url": "http://localhost:3000/sse"
}
}
}Use the standard server deployment practices for Node-based services. If you expose the server publicly, consider rate limiting and authentication for MCP endpoints. Monitor the health endpoint regularly to verify availability.
If you run in Docker, keep your Docker images up to date and pin versions to avoid unexpected changes. For local development, ensure you restart the server after dependency updates to load new tooling.
If the SSE endpoint is unreachable, verify the server is running and listening on port 3000. Check you can reach http://localhost:3000/health for a quick status check. Confirm your firewall or network settings allow traffic to the server.
If you see CLI or generation errors, ensure the Node environment is set correctly. The default environment values include PORT=3000, MCP_TRANSPORT=sse, and NODE_ENV=production. Adjust as needed for your environment.
Provides a quick overview of patterns and available tools for Android MCP usage.
Offers full architecture documentation covering Data, Domain, and UI layers.
Returns Jetpack Compose UI patterns to guide UI development.
Gives guidance on module structure and dependencies for Android projects.
Delivers build configuration details and Gradle convention plugins.
Describes testing approaches and use of test doubles.
Generates a complete feature module code scaffold.
Generates a ViewModel with UiState scaffolding.
Generates an offline-first repository pattern.
Enables search across all documentation.