Android ADB

Android ADB

landicefu

Connects to Android devices through ADB to execute shell commands, manage apps, transfer files, and capture screenshots. Enables AI assistants to automate Android development and testing tasks.

Provides a bridge to Android devices through ADB, enabling device management, shell command execution, app installation, screenshot capture, and file transfer across connected Android devices.

34579 views9Local (stdio)

What it does

  • Execute shell commands on Android devices
  • Install and uninstall Android applications
  • Transfer files between computer and Android devices
  • Capture screenshots from Android devices
  • Launch applications on connected devices
  • Manage multiple Android devices simultaneously

Best for

Android developers testing apps on devicesQA teams automating device testing workflowsDevOps engineers managing Android device farms
Works with multiple connected devicesScreenshots can be saved locally or copied to clipboardRequires ADB installation and device debugging enabled

About Android ADB

Android ADB is a community-built MCP server published by landicefu that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage Android devices with ADB: execute shell commands, install apps, capture screenshots, and transfer files for effic It is categorized under developer tools.

How to install

You can install Android ADB in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

Android ADB is released under the ISC license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Android ADB MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to interact with Android devices through the Android Debug Bridge (ADB). This server bridges the gap between AI capabilities and Android device management, allowing for seamless automation of Android development and testing operations.

⚙️ Quick Setup

Add the server to your MCP configuration file:

{
  "mcpServers": {
    "android-adb": {
      "command": "npx",
      "args": ["-y", "@landicefu/android-adb-mcp-server"],
      "env": {},
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Configuration Locations

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
  • Cline/Roo Code: ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json (macOS)
  • For Windows/Linux, check the equivalent application support directories

After configuring, restart your AI assistant to load the new server configuration.

📋 Prerequisites

  • ADB (Android Debug Bridge) must be installed and available in your system PATH
  • For clipboard functionality:
    • macOS: osascript (built-in)
    • Windows: PowerShell (built-in)
    • Linux: xclip (install via apt-get install xclip or equivalent)
  • Node.js 16.x or higher

🚀 Features

  • Connect to and manage multiple Android devices
  • Execute shell commands on Android devices
  • Install and uninstall applications
  • Push and pull files between local system and Android devices
  • Launch applications on Android devices
  • Take screenshots and save them locally or copy to clipboard
  • Smart device selection when multiple devices are connected

🛠️ Available Tools

ToolDescriptionRequired ParametersOptional Parameters
adb_devicesList connected devicesNoneNone
adb_shellExecute shell commandscommanddevice_id
adb_installInstall APK filespathdevice_id
adb_uninstallUninstall applicationspackage_namedevice_id
adb_list_packagesList installed packagesNonedevice_id, filter
adb_pullPull files from deviceremote_path, local_pathdevice_id
adb_pushPush files to devicelocal_path, remote_pathdevice_id
launch_appLaunch an applicationpackage_namedevice_id
take_screenshot_and_saveTake and save screenshotoutput_pathdevice_id, format
take_screenshot_and_copy_to_clipboardTake screenshot to clipboardNonedevice_id, format

Device Management

The server intelligently handles device selection:

  • If only one device is connected, it will be used automatically
  • If multiple devices are connected, you must specify a device_id parameter
  • If no devices are connected, an error will be returned

Screenshot Path Resolution

When specifying the output_path for saving screenshots, the path is resolved as follows:

  • Absolute paths are used as-is
  • Paths starting with ~ are expanded to the user's home directory
  • Relative paths are resolved relative to the user's home directory

This ensures that screenshots are saved to a location where the MCP server has write permissions.

🔍 Troubleshooting

Common Issues

  1. "ADB is not available" error

    • Ensure ADB is installed and in your system PATH
    • Verify by running adb version in your terminal
  2. "No Android devices connected" error

    • Check if your device is properly connected with adb devices
    • Ensure USB debugging is enabled on your device
    • Try restarting ADB with adb kill-server followed by adb start-server
  3. "Multiple devices connected" error

    • Specify the device_id parameter in your tool call
    • Get the list of available devices with the adb_devices tool
  4. Screenshot to clipboard not working

    • Ensure the required platform-specific tools are installed

🔧 Alternative Installation Methods

Option 1: Install from npm

# Install globally
npm install -g @landicefu/android-adb-mcp-server

# Or install locally in your project
npm install @landicefu/android-adb-mcp-server

Option 2: Manual Installation from Source

  1. Clone the repository:

    git clone https://github.com/landicefu/android-adb-mcp-server.git
    cd android-adb-mcp-server
    
  2. Install dependencies and build:

    npm install
    npm run build
    
  3. Configure with direct path:

    {
      "mcpServers": {
        "android-adb": {
          "command": "node",
          "args": ["/path/to/android-adb-mcp-server/build/index.js"],
          "env": {},
          "disabled": false,
          "alwaysAllow": []
        }
      }
    }
    

📄 License

This project is licensed under the ISC License - see the LICENSE file for details.

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Alternatives

Related Skills

Browse all skills
penpot-uiux-design

Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library".

19
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
ai-sdk

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

6
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

3