Skip to main content
Glama
desamtralized

ADB Screenshot MCP Server

adb_connect_wifi

Connect to Android devices over WiFi using ADB for remote management and control. Provide the device's IP address to establish wireless connectivity.

Instructions

Connect to an Android device over WiFi using ADB

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ip_addressYesIP address of the Android device
portNoPort number (default: 5555)5555

Implementation Reference

  • Handler for the adb_connect_wifi tool: executes `adb connect` command with provided IP and port, handles errors, and returns success message.
    case "adb_connect_wifi": {
      const { ip_address, port = "5555" } = args as {
        ip_address: string;
        port?: string;
      };
    
      const { stdout, stderr } = await execAsync(`adb connect ${ip_address}:${port}`);
      
      if (stderr && stderr.includes("failed")) {
        throw new McpError(ErrorCode.InternalError, `ADB connection failed: ${stderr}`);
      }
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully connected to ${ip_address}:${port}\n${stdout}`,
          },
        ],
      };
    }
  • Schema definition for adb_connect_wifi tool, including input schema with ip_address (required) and optional port.
    {
      name: "adb_connect_wifi",
      description: "Connect to an Android device over WiFi using ADB",
      inputSchema: {
        type: "object",
        properties: {
          ip_address: {
            type: "string",
            description: "IP address of the Android device",
          },
          port: {
            type: "string",
            description: "Port number (default: 5555)",
            default: "5555",
          },
        },
        required: ["ip_address"],
      },
    },
  • src/index.ts:29-114 (registration)
    Registration of adb_connect_wifi tool in the ListTools response.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "adb_connect_wifi",
            description: "Connect to an Android device over WiFi using ADB",
            inputSchema: {
              type: "object",
              properties: {
                ip_address: {
                  type: "string",
                  description: "IP address of the Android device",
                },
                port: {
                  type: "string",
                  description: "Port number (default: 5555)",
                  default: "5555",
                },
              },
              required: ["ip_address"],
            },
          },
          {
            name: "adb_screenshot",
            description: "Take a screenshot of the connected Android device",
            inputSchema: {
              type: "object",
              properties: {
                output_path: {
                  type: "string",
                  description: "Local path to save the screenshot (default: screenshot.png)",
                  default: "screenshot.png",
                },
                device_id: {
                  type: "string",
                  description: "Device ID/serial (optional, uses first device if not specified)",
                },
              },
              required: [],
            },
          },
          {
            name: "adb_list_devices",
            description: "List all connected ADB devices",
            inputSchema: {
              type: "object",
              properties: {},
              required: [],
            },
          },
          {
            name: "adb_disconnect",
            description: "Disconnect from a WiFi ADB device",
            inputSchema: {
              type: "object",
              properties: {
                ip_address: {
                  type: "string",
                  description: "IP address of the device to disconnect from",
                },
                port: {
                  type: "string",
                  description: "Port number (default: 5555)",
                  default: "5555",
                },
              },
              required: ["ip_address"],
            },
          },
          {
            name: "adb_device_info",
            description: "Get information about a connected device",
            inputSchema: {
              type: "object",
              properties: {
                device_id: {
                  type: "string",
                  description: "Device ID/serial (optional, uses first device if not specified)",
                },
              },
              required: [],
            },
          },
        ],
      };
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Connect') but does not describe what happens on success/failure, whether it persists connections, requires authentication, or has side effects like disconnecting other sessions. For a connectivity tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It is front-loaded with the core purpose and uses precise terminology, making it easy to parse quickly without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a connectivity tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral outcomes, error handling, or return values, which are crucial for an agent to use it effectively. The high schema coverage does not compensate for these missing contextual elements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear documentation for both parameters (ip_address and port with default). The description adds no additional meaning beyond the schema, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Connect to an Android device over WiFi') and the technology used ('using ADB'), which distinguishes it from sibling tools like adb_disconnect (disconnection) or adb_screenshot (capturing screenshots). It precisely identifies both the verb and resource without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing ADB setup or device WiFi debugging enabled), exclusions, or comparisons to sibling tools like adb_connect_wired, if such existed. Usage context is implied but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/desamtralized/adb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server