Metro MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

                ? await ctx.exec(`${adbPrefix(target.id)} shell ${ra}sh -c 'dd if="${path}" bs=${limit} count=1 2>/dev/null | base64'`)

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const child = spawn(process.execPath, [entry, 'serve', ...args], {

    entries = fs.readdirSync(getConfigDir());

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update server.json version
        if: ${{ inputs.version != '' }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add metro-mcp -- npx -y metro-mcp

{
  "mcpServers": {
    "metro-mcp": {
      "args": [
        "-y",
        "metro-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.metro-mcp]
command = "npx"
args = ["-y", "metro-mcp"]

{
  "mcpServers": {
    "metro-mcp": {
      "args": [
        "-y",
        "metro-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "metro-mcp": {
      "args": [
        "-y",
        "metro-mcp"
      ],
      "command": "npx"
    }
  }
}