An MCP server that provides control over Android devices through ADB. Offers device screenshot capture, UI layout analysis, package management, and
Android MCP becomes available to MCP clients through the android mcp mcp server. An MCP server that provides control over Android devices through ADB. Offers device screenshot capture, UI layout analysis, package management, and ADB command execution capabilities.
An MCP (Model Context Protocol) server that provides programmatic control over Android devices through ADB (Android Debug Bridge). This server exposes various Android device management capabilities that can be accessed by MCP clients like Claude desktop and Code editors (e.g. Cursor)
Once connected, the assistant can call these 3 tools directly:
Windows — %APPDATA%\Claude\claude_desktop_config.jsonmacOS — ~/Library/Application Support/Claude/claude_desktop_config.jsonScenario — Configuration RequiredSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. Android MCP sits in that group, and the shape of its toolset — Windows, macOS, Scenario — tells you what it is really for. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Scenario | Configuration Required |
{
"mcpServers": {
"android": {
"command": "path/to/uv",
"args": ["--directory", "path/to/android-mcp-server", "run", "server.py"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.