- Servers on more machines: Settings › Machines › Connect another machine makes a one-line command for a second VPS or a home server (any system Playkeeper runs on, with at least 2 CPU cores, 3 GB of memory and 5 GB of free disk). Its CPU needn't match the dashboard machine's: each machine, x86_64 or 64-bit ARM, installs and updates its own build. On a new machine it installs Playkeeper without a dashboard of its own; on one that already runs Playkeeper, it's
sudo playkeeper join …. The machine dials out to your dashboard's address and port and reconnects by itself, so no port opens on it for Playkeeper; its servers' game ports need opening there as usual. Its servers show up on Home and in the sidebar with the others. Each code works once, for 30 minutes, and the fingerprint in the command proves the machine found your dashboard. Open the dashboard at its IP address or domain name to get the command, and usesudo playkeeper leaveon the machine to disconnect it. - AI agents: Settings › AI agents shows the dashboard's MCP address and makes a token for each AI tool, such as Claude or Cursor, for 30, 60, 90 or 365 days and for all servers or some. A token has a Viewer's rights (status, players, the console and crashes, and searching for plugins and mods), a Moderator's (also start and stop, backups and the allowlist) or an Admin's (also console commands, and installing and removing plugins and mods), and never more than your own account: it stops working if you're removed from the team, your role is lowered or you lose a server it's for. What agents do shows up there and in the activity log. Over SSH,
sudo playkeeper mcpserves the same tools with the owner's rights, for that machine's servers.
More machines and AI agents
Servers on a second VPS or a home server, all in one dashboard, and AI tools such as Claude or Cursor managing them over MCP.
Can't find it?
Ask in GitHub Discussions. Answers are public, so the next person finds them too.