Ghost Hands MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

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.

        proc = subprocess.run(

    env = dict(os.environ)

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 ghost-hands -- uvx ghost-hands

{
  "mcpServers": {
    "ghost-hands": {
      "command": "uvx",
      "args": [
        "ghost-hands"
      ]
    }
  }
}

[mcp_servers.ghost-hands]
command = "uvx"
args = ["ghost-hands"]

{
  "mcpServers": {
    "ghost-hands": {
      "command": "uvx",
      "args": [
        "ghost-hands"
      ]
    }
  }
}

{
  "servers": {
    "ghost-hands": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ghost-hands"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GHOST_HANDS_DRIVER (Session body for the MCP server: fake (default), chromium, simphone, or android), GHOST_HANDS_START_URL (Optional URL opened on the first perceive call when a real body is selected), GHOST_HANDS_APPROVER (Set to phone to route approval asks through the PhoneApprover (requires the Android bridge env vars)).