Set up Aster

1. 1

   Install the MCP server

   The server is an npm package, aster-mcp, currently version 0.1.16. Install it globally on the machine that will stay awake — a laptop, a desktop, a NAS or a mini PC.

   terminal Copy

   npm install -g aster-mcp

   Node.js >= 20 is required. Running the server inside Termux on the phone itself is untested and unsupported; use the app's on-device MCP mode instead.

2. 2

   Start the server

   One command brings up all three listeners: 5987 for the Device WebSocket, 5988 for the API + MCP HTTP, 5989 for the Web dashboard. The terminal prints the exact WebSocket address to type into the phone.

   terminal Copy

   aster start

   Keep these ports on your LAN or your tailnet. Do not port-forward 5987 or 5988 to the public internet — the device link is plain ws:// and terminates no TLS of its own.

3. 3

   Install the Android companion

   Download the latest APK from GitHub Releases and sideload it. It runs on Android 8.0+ (API 26) and needs no root. Use your daily phone, or a spare Android you want to hand over to your AI entirely.

   Download the APK from GitHub Releases

   Accessibility Service is the one permission Aster cannot work without — it is what reads the screen and drives taps. Notifications, SMS, phone, location and storage are each optional and asked for separately.

4. 4

   Point the phone at the server

   Open Aster on the phone, enter the WebSocket address the terminal printed — ws://<server-ip>:5987 — and tap Connect. For a dedicated AI phone, plug it into a charger and leave it there.

   The address is a LAN IP and is only valid on that network. If you move between Wi-Fi networks, join both ends to Tailscale and use the stable tailnet address instead.

5. 5

   Approve the device

   A new device arrives as pending and can connect but not be commanded. Approve it from the CLI, or click Approve in the dashboard at http://localhost:5989.

   terminal Copy

   aster devices approve <deviceId>

   A device left pending is the single most common setup failure: it shows as connected while every tool call times out. There are no tokens or per-device keys — approval is the whole access-control model.

6. 6

   Point your AI client at the MCP endpoint

   Add Aster to your client as a streamable-HTTP MCP server at http://localhost:5988/mcp. All 49 tools then appear namespaced aster_*, so a call looks like aster_take_screenshot.

   .mcp.json Copy

   {
     "mcpServers": {
       "aster": {
         "type": "http",
         "url": "http://localhost:5988/mcp"
       }
     }
   }

   Per-client instructions — Claude, OpenClaw, AnythingLLM and OpenAlly — are below.

   One address per audience: 5987 goes in the phone, 5988/mcp goes in the AI client, 5989 goes in your browser. Pasting the wrong port into the wrong app is the second most common setup failure.

• Claude Code and Claude Desktop

  Add the entry below to your project's .mcp.json, or to the Claude Desktop MCP settings, and restart the client. Aster registers 49 tools, every one of them prefixed aster_.

  .mcp.json Copy

  {
    "mcpServers": {
      "aster": {
        "type": "http",
        "url": "http://localhost:5988/mcp"
      }
    }
  }

• OpenClaw, MoltBot and ClawdBot

  Aster ships as a skill on ClawHub, the registry agent clients such as OpenClaw, MoltBot and ClawdBot install skills from. Install it from the hub, or fetch the skill file straight from the repository if your client takes a raw URL.

  terminal Copy

  clawhub install aster
  
  # or take the skill file directly:
  curl -O https://raw.githubusercontent.com/satyajiit/aster-mcp/main/skill/SKILL.md

  The Aster skill on ClawHub

• AnythingLLM and any MCP client

  There is nothing Aster-specific to install. The server speaks standard streamable-HTTP MCP, so any compliant client works by pointing it at the endpoint. On a LAN, swap localhost for the server machine’s address.

  endpoint Copy

  http://localhost:5988/mcp

• OpenAlly

  OpenAlly runs on the same phone and drives Aster over Android Binder IPC — no server, no network hop, nothing to configure. Install both apps, approve the on-device handshake once, and OpenAlly has the full on-device action catalog (77 actions, unprefixed). This is the only path that needs no MCP endpoint at all.

  OpenAlly.ai

Every path above reaches the same 49 server-side tools except OpenAlly, which talks to the phone directly and therefore sees the on-device catalog instead. The server itself is on npm as aster-mcp.

Checking it actually works

Two commands separate “the server is up” from “the phone is reachable”. Run both before blaming the AI client.

aster status
curl http://localhost:5988/api/health

aster status

Prints the human-readable snapshot the running server writes to ~/.aster/status.json: the advertised addresses, and every device with its approval state. A device listed as pending is connected but cannot be commanded yet.

curl http://localhost:5988/api/health

Returns { "status": "ok", "timestamp": ... }. This is the endpoint to poll from scripts and monitors; GET /api/stats next to it returns device counts.

Your AI client

Ask it to list its tools. You should see 49 names, all beginning aster_ — aster_take_screenshot is the cheapest one to try first. If the list is empty, the client never reached http://localhost:5988/mcp; if a call hangs, the device is still pending.

Still stuck? The FAQ and troubleshooting page covers pending devices, ws:// versus wss://, firewall ports and silent voice calls.