MCP server exposing Android Debug Bridge (ADB) capabilities as tools and resources.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"adb-automation-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# adb-automation-mcp <!-- mcp-name: io.github.allaudin/adb-automation-mcp --> [](https://github.com/allaudin/adb-automation-mcp/actions/workflows/ci.yml) [](https://pypi.org/project/adb-automation-mcp/) An MCP server exposing Android Debug Bridge (ADB) capabilities as typed, documented tools and resources. **[Full documentation](https://allaudin.github.io/adb-automation-mcp/)** — architecture, decision log, per-tool reference, and client integration guides. ## Install ```bash uvx adb-automation-mcp # or pip install adb-automation-mcp ``` ## Quickstart ```bash uv sync uv run adb-automation-mcp ``` Talks to the `adb` binary on `PATH` by default. For real-device setup, the fake backend, the full tool list, and per-client integration guides (Claude Code, Claude Desktop, ...), see the [docs site](https://allaudin.github.io/adb-automation-mcp/). ## Installation prompt Prefer not to configure this by hand? Hand the [AI-assisted install prompt](https://allaudin.github.io/adb-automation-mcp/integrations/ai-assisted-install/) to an AI coding assistant that can run shell commands and edit MCP config (Claude Code, GitHub Copilot in agent mode, ...) — it detects/installs `uv`, resolves `adb`'s absolute path, and registers this server for you. ## MCP client configuration Add this to your client's `mcp.json` (e.g. Claude Desktop's config, or a Claude Code project's `.mcp.json`). Every real-device env var is shown below — all are optional, see the [full reference](https://allaudin.github.io/adb-automation-mcp/#running-it) for defaults and details (including `ADB_AUTOMATION_BACKEND`, a testing-only switch to the fake in-memory backend, not something a real client config needs): ```json { "mcpServers": { "adb-automation-mcp": { "command": "uvx", "args": ["adb-automation-mcp"], "env…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.