DeepADB is an MCP server that exposes Android Debug Bridge functionality to AI agents for interacting with connected Android devices or, in on-device mode, executing commands locally on the device. It supports device inspection, app and file management, logs, diagnostics, UI automation, screenshots, screen recording, testing, and multi-device operations over stdio, HTTP/SSE, or WebSocket.
From the registry: Full-featured ADB MCP server — 204 tools across 45 modules, from UI to baseband.
$ npm install && npm run buildPlease install the `deepadb` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js and npm** — Node.js is required to install dependencies, build, and run the DeepADB server.
- **Install Android Debug Bridge (ADB)** — DeepADB's default PC-side mode communicates with Android devices through the ADB binary.
- **Connect and authorize an Android device** — Attach an Android device over USB or otherwise make a device available to ADB, and authorize the host for debugging.
- **Install project dependencies and build from source** — The README shows running DeepADB from a local checkout by installing npm dependencies and building the project before use. Run: `npm install && npm run build`
Canonical MCP server config (stdio transport):
- command: `node`
- args: ["<path-to-deepadb>/build/index.js"]
- optional environment variables:
- `DA_LOCAL`: Override auto-detection of on-device vs PC-side mode. Set to true to force on-device LocalBridge mode or false to force ADB mode. (example: `<true-or-false>`)
- `DA_HTTP_PORT`: If set, starts the server in HTTP/SSE mode instead of plain stdio on the given port. (example: `<port>`)
- `DA_WS_PORT`: If set, enables WebSocket mode on the given port. README notes this requires the ws package to be installed. (example: `<port>`)
- `DA_GRAPHQL_PORT`: If set, enables the optional GraphQL API alongside the main transport. README notes this requires the graphql package to be installed. (example: `<port>`)
Note: README documents multiple transports (stdio, HTTP/SSE, WebSocket), but the provided canonical MCP client configuration example is stdio using the built build/index.js entrypoint. HTTP/SSE can be enabled by setting DA_HTTP_PORT before launch, but no explicit MCP client URL example is provided. The README appears truncated near the end.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.An MCP Server for computer-use in Windows OS