Phone MCP Server

What does “Phone” MCP Server do?

The Phone MCP Server is a plugin for the Model Context Protocol (MCP) that enables users to control their Android phones remotely using ADB (Android Debug Bridge) commands. By integrating with MCP-compatible clients, the Phone MCP Server acts as a bridge between AI assistants and Android devices, allowing for automation, device management, and real-time interactions. Developers can leverage this server to execute phone-related actions such as launching apps, sending messages, taking screenshots, or retrieving device information—all via standardized MCP tools. This extends the capabilities of AI-driven workflows to include direct physical device control, streamlining testing, development, and automation tasks that require mobile hardware interaction.

List of Prompts

(No prompt templates are mentioned in the repository.)

List of Resources

(No specific MCP resources are described in the repository.)

List of Tools

• ADB Command Execution
  The Phone MCP plugin exposes tools that allow clients to send ADB (Android Debug Bridge) commands to connected Android devices. These tools can be used to automate device operations such as launching applications, simulating input, querying device status, and more.

(The exact tool names and arguments are not listed, but the general function is “ADB command execution” as per the project’s purpose and description.)

Use Cases of this MCP Server

• Automated Device Testing
  Developers and QA engineers can automate the testing of Android apps by issuing ADB commands to interact with the device, simulate user actions, and collect logs or screenshots.
• Application Deployment
  The server can streamline the process of installing, updating, or uninstalling applications on one or multiple Android devices remotely.
• Device Management and Monitoring
  IT administrators can perform remote diagnostics, check device status, and enforce actions such as restarting, locking, or configuring devices.
• Workflow Automation
  Integrate phone control into larger automation pipelines, enabling tasks like sending notifications, retrieving messages, or triggering device actions as part of an AI-driven workflow.
• Educational and Demonstration Purposes
  Educators can showcase Android device usage, automation, or app features in real-time during classes or webinars by remotely controlling the device.

How to set it up

Windsurf

1. Ensure you have Node.js and Windsurf installed.
2. Locate your Windsurf configuration file.
3. Add the Phone MCP Server using a JSON snippet under the mcpServers section.
4. Save the configuration and restart Windsurf.
5. Verify the server appears in the available MCP servers list.

"mcpServers": {
  "phone-mcp": {
    "command": "phone-mcp",
    "args": []
  }
}

Claude

1. Install Node.js and ensure Claude is set up.
2. Edit Claude’s configuration file.
3. Insert the Phone MCP Server configuration in the mcpServers block.
4. Save and restart Claude.
5. Confirm the MCP server is accessible in the Claude UI.

"mcpServers": {
  "phone-mcp": {
    "command": "phone-mcp",
    "args": []
  }
}

Cursor

1. Install Node.js and Cursor.
2. Find and open the Cursor configuration file.
3. Add the Phone MCP Server under the mcpServers section.
4. Save changes and restart Cursor.
5. Ensure the server is detected in the MCP integration list.

"mcpServers": {
  "phone-mcp": {
    "command": "phone-mcp",
    "args": []
  }
}

Cline

1. Make sure you have Node.js and Cline installed.
2. Open the Cline configuration file.
3. Add the Phone MCP Server in the mcpServers section.
4. Save and restart Cline.
5. Check the MCP server status in Cline.

"mcpServers": {
  "phone-mcp": {
    "command": "phone-mcp",
    "args": []
  }
}

Securing API Keys with Environment Variables

If your MCP server requires API keys or secrets, store them in environment variables:

"mcpServers": {
  "phone-mcp": {
    "command": "phone-mcp",
    "args": [],
    "env": {
      "API_KEY": "your-api-key"
    },
    "inputs": {
      "device_id": "your-device-id"
    }
  }
}

(Adjust variable names as needed for your environment.)

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "phone-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “phone-mcp” to the actual name of your MCP server and replace the URL with your own MCP server URL.

Overview

Based on the above, Phone MCP provides a clear and practical tool for ADB command execution, but lacks documentation for prompts and resources. The setup is standard, and API key security is acknowledged. Sampling and Roots are not addressed.

Our opinion

This MCP server is highly specialized and useful for those needing Android device automation through MCP, but the lack of detailed documentation on prompts, resources, and sampling support limits its flexibility and ease of integration. For users who specifically need ADB control via MCP, it is solid, but broader MCP users may find it lacking in features and documentation.

MCP Score