Deepadb
Wire your coding agent to real Android devices for UI inspection, shell commands, and low-level diagnostics without leaving the chat.
Overview
io.github.fullread/deepadb is a MCP server for the Build phase that exposes 204 Android Debug Bridge tools across 45 modules so agents can control and diagnose devices from UI through baseband.
What is this MCP server?
- 204 MCP tools organized across 45 modules from UI automation through baseband-level operations
- stdio npm package `deepadb` (v1.1.3) for local agent attachment
- Breadth covers typical solo-builder needs: installs, logcat, screenshots, package management, and deeper device controls
- GitHub source at fullread/DeepADB for self-hosted or forked workflows
- Suited to repeatable device QA scripts the agent can run after each build
- Server version 1.1.3
What problem does it solve?
You need dozens of adb workflows in chat, but hand-rolling shell scripts for every device task does not scale for one-person mobile shipping.
Who is it for?
Indie Android developers and agent builders who routinely test on hardware or emulators and want MCP-native device control during Build and Ship checks.
Skip if: Teams with no Android surface area, builders who only ship web SaaS, or anyone unwilling to run adb with physical device security discipline.
What do I get? / Deliverables
After registering deepadb, your agent can invoke structured ADB operations during builds and device QA instead of you pasting opaque shell commands.
- Agent-callable adb operations across 45 functional modules
- Repeatable device inspection and automation without custom MCP glue code
- Local stdio MCP attachment documented via server.json v1.1.3 metadata
Recommended MCP Servers
Journey fit
DeepADB is canonical on Build because it extends the agent’s toolchain for shipping and debugging Android apps and automation, not for early market research. Agent-tooling fits a stdio MCP that exposes 204 ADB-backed tools so Claude/Cursor can drive devices like an IDE extension.
How it compares
Device-control MCP integration, not a mobile app generator or Play Store launch checklist skill.
Common Questions / FAQ
Who is io.github.fullread/deepadb for?
It is for solo builders and small teams shipping Android products who want their Claude Code, Cursor, or Codex agent to run adb-backed diagnostics and automation through MCP.
When should I use io.github.fullread/deepadb?
Use it during Build and Ship when you are integrating features, running on-device tests, or debugging UI and system behavior that requires live adb access.
How do I add io.github.fullread/deepadb to my agent?
Install the npm package `deepadb` (registry identifier deepadb), configure stdio transport in your agent’s MCP settings, and point the server entry at the published binary per the DeepADB GitHub README.