Any MCP client

Any client that speaks MCP over Streamable HTTP can use PlayOn. Named guides exist for Cursor, Claude Code, Codex, OpenClaw, and Hermes — this page is the portable contract. Overview: External agents (MCP).

Endpoint

Item	Value
URL	http://<playon-host>:<port>/mcp (Home default API port is often 8787)
Auth	Authorization: Bearer <access_token>

Create the token in Settings → External agents (MCP).

Minimal client config

{
  "mcpServers": {
    "playon": {
      "url": "http://<host>:8787/mcp",
      "headers": {
        "Authorization": "Bearer playon_…"
      }
    }
  }
}

Example

Using PlayOn MCP, install Minecraft, start a LAN server, publish the player panel, and return the /play link.

Requirements

• Client can open HTTP(S) to the host.
• Token not revoked; Owner (or permitted operator) minted it.
• Confirm-gated tools need UI approval unless auto-approve is on for that token.

What not to do

• Do not expose MCP to the public internet without TLS and tight network controls.
• Do not put PATs in player panels, Discord, or event pages.