01 / Project prompt
Exact steps, not vibes.
The creator desk gives the agent the SDK version, login command, and the rules that keep the game on Loki.
Product / Agents
Built for the Agentic AI Era.
Cursor, Claude Code, and similar tools should not invent a backend. Loki gives them one package, one protocol, and one set of platform rules.
Canonical rules
One source. No invented servers.
Agents get the same instructions every time: install Loki, keep gameplay in the client, and deploy a finished build. They do not write a disposable server.js.
docs.lokiplay.ccFor humans and agents
/agentsCanonical integration rules/mcpConnect Loki as an MCP server/llms.txtShort product summary/llms-full.txtEvery doc in one fileHow the desk works
You approve. The agent implements.
02 / Device login
No pasted tokens.
The CLI opens a browser code. You sign in and approve the terminal. The agent never asks for a secret.
03 / Validate + deploy
Fail before players see it.
The same checks the CLI runs are the checks the agent must pass. A blocked build never becomes a playable URL.
One plugin. Zero infrastructure sprawl.
Hand the missing backend to Loki.
Start free with private hosting, add multiplayer when you need it, and go public only when you are ready.