antics-mcp
OfficialThe antics-mcp server lets AI agents deploy HTML games as playable multiplayer experiences and manage projects/leaderboards.
deploy_game: Upload a single HTML file to instantly get a multiplayer URL. No login required for ephemeral keyless rooms (up to 8 players, lasting 24 hours); provide aprojectIdfor persistent deployments.create_project: Register a named project and receive its ID, a publishable key (pk_), and a secret key (sk_). Requires login.get_leaderboard: Fetch top scores for a project's leaderboard (optionally filtered by board name). Requires login.list_projects: List all projects associated with your account. Requires login.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@antics-mcp deploy a multiplayer pong game"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
antics-mcp
Multiplayer for your game, in one prompt. An MCP server that lets an AI agent generate a web game and deploy it to a playable multiplayer URL — rooms, live state sync, and leaderboards — inside a single conversation.
AI can write a whole game — a single HTML file or a multi-file project — but it can't stand up
a server, so everything it builds is single-player. antics-mcp is the missing piece: your
agent writes the game, calls one tool, and hands you back a link your friends can open. No
backend, no player accounts.
→ antics.gg · full API in one file: antics.gg/llms.txt
Install
Claude Code:
claude mcp add antics -- npx -y antics-mcpClaude Desktop / Cursor / any MCP client — add to your MCP config
(claude_desktop_config.json, Cursor's mcp.json, etc.):
{
"mcpServers": {
"antics": {
"command": "npx",
"args": ["-y", "antics-mcp"]
}
}
}Then just ask: “Make a 2-player game and deploy it.” The agent writes it, calls deploy_game,
and returns a playable URL — no copy-paste, no site visit, no login.
Related MCP server: agent-game-engine
Tools
Tool | What it does | Login? |
| Deploy a game ( | No |
| Create a project; returns its id, publishable key ( | Yes |
| Read a project's leaderboard (top scores). | Yes |
| List your projects. | Yes |
| Brand how a project's room links unfurl on social — title, description, and image. | Yes |
deploy_game works without any login — it returns an ephemeral, keyless URL you can share
immediately (rooms hold 8 players and last 24h). To persist links + leaderboards and raise the
limits, sign in once with npx antics-cli login (GitHub), then the owner-scoped tools unlock and
deploy_game can target a project.
How the multiplayer works
Your agent doesn't need to know any of this up front — antics.gg/llms.txt
is the complete API in one file, written so an LLM can integrate it one-shot. In brief: a game
calls joinRoom({}), shared room state is host-authoritative with per-player slices, writes
coalesce to ~20 Hz, and a leaderboard is one submitScore() call. The deployed game runs at a
/r/<code> URL with an invite link + QR built in.
Links
Site: https://antics.gg
Docs / API reference: https://antics.gg/docs · https://antics.gg/llms.txt
Try a demo (no install): the four games on antics.gg were each generated one-shot from the docs.
Available Tools
4 toolscreate_projectB
Create a project; returns its id, publishable key (pk_), and secret key (sk_, shown once).
Inputs: name (required).
deploy_gameA
Deploy a single HTML game file and get a playable multiplayer URL (keyless if no projectId).
Inputs: html (required), projectId.
get_leaderboardB
Read a project's leaderboard (top scores).
Inputs: projectId (required), board.
list_projectsB
List your projects (requires login).
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct action: project creation, game deployment, leaderboard retrieval, and project listing. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_project, deploy_game), making them predictable and easy to understand.
With only 4 tools, the server is well-scoped for its apparent purpose: project creation, game deployment, and leaderboard access. Each tool serves a clear function without bloat.
The tool surface covers core operations (create, deploy, list, read scores) but lacks update and delete tools for projects, and there is no tool for managing users or game configurations.
Maintenance
Related MCP Connectors
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
Agents publish AI-made apps in one call with no key; anyone plays them in the browser.
Publish, test and share browser games on PlayDrop from your AI agent.
Publish AI-made browser games and get a shareable URL. Update, test and read player feedback.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to build and test games headlessly using the llmgine game engine, with tools for world creation, prefab definition, spawning, acting, and simulation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, run, and debug 2D games in a sandboxed engine, providing tools for simulation, state inspection, and quality validation.1MIT
- AlicenseAqualityBmaintenanceLet coding agents play, test and tune your 2D web game. The debuff MCP server attaches to the game you have open (or runs a headless copy) and gives agents live state, explained and source-mapped errors, frame timings, typed params, deterministic replays and rewind, scenario tests and fuzz playtesting. Everything an agent does shows in your dev panel, where you can undo it.2112MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to publish and manage HTML5 browser games, giving each game its own address and catalogue page with leaderboards, cloud saves, player clips, daily stats, versioning, and rollback.1MIT