antics-mcp is an MCP server for deploying web games to playable multiplayer URLs, with built-in rooms, real-time state synchronization, and leaderboards, with the goal of completing the process from generation to deployment within a single conversation.
Purpose AI can write complete games (a single HTML file or a multi-file project), but it cannot start a server on its own, so the games it builds are usually single-player. antics-mcp serves as a complementary step: after the agent writes a game, it calls one tool and gets back a playable link that a friend can open, with no backend and no player account required.
Main capabilities
- Multiplayer support: deployed games run under a /r/<code> URL, with built-in invite links and QR codes.
- Rooms and state synchronization: games call joinRoom({}) to join a room; shared room state uses a host-authoritative model and supports per-player slices, with writes merged to about 20 Hz.
- Leaderboards: submit a score with a single submitScore() call.
- Deployment without login: deploy_game requires no login and returns a temporary keyless URL that can be shared immediately; rooms hold 8 players and are valid for 24 hours.
- Persistence and higher limits: after logging in (via npx antics-cli login using GitHub login), links and leaderboards can be persisted and limits increased, while owner-scoped tools are unlocked, and deploy_game can specify a project.
How to use Suitable for Claude Desktop, Cursor, or any MCP client: add antics-mcp to the MCP configuration (such as claude_desktop_config.json, Cursor's mcp.json, etc.). Then simply prompt "make a 2-player game and deploy it," and the agent will write the game, call deploy_game, and return a playable URL, with no copy-pasting, no visiting a site, and no login.
Use cases
- Quickly turn AI-generated web games into multiplayer playable versions.
- Create, share, and play multiplayer mini-games directly in a conversation.
- Scenarios that need rooms, state synchronization, and leaderboards but do not want to build a backend or account system.
Limitations
- When not logged in, deployment links are temporary, rooms are capped at 8 players, and they are valid for 24 hours.
- Persistent links, leaderboards, and higher limits require login.
- The multiplayer synchronization mechanism is a host-authoritative modelwith writes merged to about 20 Hz.
Related links
- Site:https://antics.gg
- Documentation/API reference:https://antics.gg/docs · https://antics.gg/llms.txt
- Full API single file: antics.gg/llms.txt
- Try the demos (no installation required): the four games on antics.gg were each generated in one pass from the documentation.
- Install and login command: npx antics-cli login
