Installation: CLI and MCP

Connect the MCP Server

Heyo's MCP server gives a coding agent tools to deploy apps, run commands in VMs, move files, read logs and metrics, follow CI runs and push images. Heyo hosts it at https://mcp.heyo.work/mcp (streamable HTTP), so there is nothing to install.

Get a token

Sign in to the dashboard at admin.us5.heyo.work and use the Get started card, or App-tokens → New token. The token starts with applb_, is confined to your namespace, and expires within 90 days. The agent can do anything in your namespace that you can, so treat the token like a password.

Claude Code

claude mcp add --transport http heyo https://mcp.heyo.work/mcp \
  --header "Authorization: Bearer applb_…"

Add --scope user to make it available in every project. Avoid --scope project: it writes the token into the project's .mcp.json, which is meant to be committed.

Other MCP clients

Any client that speaks streamable HTTP takes the URL and an Authorization header:

{
  "mcpServers": {
    "heyo": {
      "type": "http",
      "url": "https://mcp.heyo.work/mcp",
      "headers": { "Authorization": "Bearer applb_…" }
    }
  }
}

Check the connection

Ask the agent to call heyo_status. It lists the services the server can reach with your token and what each one reports. Then describe what you want:

Create a sandbox VM in my namespace with an 8 GB workspace disk and install Node 22 in it.

If a tool returns a 401, the token is missing, expired or mistyped. Mint a new one and update the header.

Next