MCP

POST https://app.machine0.io/mcp

Streamable HTTP transport, stateless, JSON responses. Gives agents the same capabilities as the CLI.

Authentication

OAuth (interactive clients) — MCP clients supporting RFC 9728 discover endpoints automatically. Claude Desktop, claude.ai custom connectors, and Claude Code handle this out of the box. API key (programmatic) — pass in the x-api-key header. Generate keys from your account settings.

Setup

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "machine0": {
      "url": "https://app.machine0.io/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http machine0 https://app.machine0.io/mcp

Other clients

Any MCP client with Streamable HTTP transport support. Point at https://app.machine0.io/mcp with OAuth or an API key header. Browser-based clients work too via OAuth — the OAuth and MCP endpoints are CORS-enabled, so tools like the MCP Inspector can connect and complete the OAuth flow directly from the browser. (The x-api-key header is for non-browser clients; browsers authenticate with OAuth.)

Tools

Category	Tools
Machines	10 — create, manage, destroy VMs
Images	10 — snapshot VMs, manage versions
SSH Keys	7 — public and managed keys
SSH Exec	1 — run commands on VMs remotely
Sizes	1 — list sizes and pricing

Managed keys

To use ssh_exec, VMs must be created with a managed key (server-side keypair). Create one with ssh_key_create_managed, then pass its ID when creating VMs. VMs with public keys cannot use ssh_exec.

Introduction

Examples

Platform

Reference

Authentication

Setup

Claude Desktop

Claude Code

Other clients

Tools

Managed keys

​Authentication

​Setup

​Claude Desktop

​Claude Code

​Other clients

​Tools

​Managed keys

Authentication

Setup

Claude Desktop

Claude Code

Other clients

Tools

Managed keys