External agents (MCP)

PlayOn exposes one tool registry to every agent entry point. In-app chat and MCP clients share the same tools, path jail, and confirm gates — only the model and transport change.

Bootstrap via MCP

After PlayOn is installed and you create the Owner account:

1. Mint an access token in Settings (below).
2. Point your agent at the MCP URL with that token.
3. Ask it to install game skills from the catalog, create servers, configure them, publish the player panel, and give you join info.

You do not need a Venice (or other) LLM key on the host for MCP-only use — the external agent brings its own model.

One-time PlayOn setup

1. Install PlayOn from Get PlayOn and create the Owner.
2. Open Settings → External agents (MCP).
3. Note the MCP URL — it looks like http://<your-host>:8787/mcp (or your published origin + /mcp).
4. Create an access token. Copy the plaintext token immediately; it is shown once.
5. Optional: enable Auto-approve confirm-gated tools only for trusted automation (actions remain audited).

Client guides

Client	Guide
Cursor	Connect Cursor
Claude Code	Connect Claude Code
Codex	Connect Codex
OpenClaw	Connect OpenClaw
Hermes Agent	Connect Hermes
Anything else	Generic MCP

Example asks (bootstrap)

Install Minecraft from the playon.games catalog, create a server for tonight’s LAN, start it, publish the player panel, and give me the /play URL.

If this laptop is too weak, add my VPS at 203.0.113.9 as a cloud node over SSH, then put the server there.

Search skills for Rust, install the official package, and bring a server up.

Example asks (ops)

List servers and restart the Minecraft instance.

Players can’t join — check ports and recent logs, then fix it.

Take a snapshot before I change configs.

Safety

• Tokens are host credentials. Revoke them in Settings if a laptop is lost.
• Confirm-gated tools still pause for host approval unless you opted into auto-approve.
• MCP is for operators — not for players.