antics MCP server
✓ VerifiedEnables AI agents to deploy web games to playable multiplayer URLs with real-time state synchronization and leaderboards.
Also known as antics-gg/antics-mcp
- Stars
- 5
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.5.1
- Last commit
- Jul 23, 2026
- License
- —
What is antics MCP?
antics enables AI agents to deploy web games to playable multiplayer URLs with real-time state synchronization and leaderboards.
Summary generated from the project's README
About antics MCP server
Deploying web games with real-time multiplayer functionality directly from an AI conversation is what antics-mcp enables. While AI agents can write game code, they typically lack the ability to host backend services. This server bridges that gap by allowing an agent to call a single tool to turn a single HTML file or a multi-file project into a playable URL featuring live state synchronization and leaderboards.
Developers can use this with Claude Code, Claude Desktop, or Cursor by adding the server via npx. The deploy_game tool provides immediate, keyless access to ephemeral rooms that support up to 8 players for 24 hours. For more permanent needs, users can sign in via GitHub to manage projects, use create_project to obtain publishable and secret keys, and utilize tools like get_leaderboard or set_share_preview to manage branding and scores.
What you can do with it
- 1Deploy a quick multiplayer gameAsk an AI agent to write a two-player game and provide a link that friends can open immediately.
- 2Manage persistent game projectsCreate a formal project to obtain unique API keys for long-term hosting and score tracking.
Written from the project's README. Every use case is checked against a quote from it.
How to install antics MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall antics MCP in Claude Code
$ claude mcp add antics-mcp -- npx -y antics-mcpInstall antics MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"antics-mcp": {
"command": "npx",
"args": [
"-y",
"antics-mcp"
]
}
}
}Install antics MCP in VS Code
.vscode/mcp.json
{
"servers": {
"antics-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"antics-mcp"
]
}
}
}Install antics MCP in VS Code CLI
$ code --add-mcp '{"name":"antics-mcp","type":"stdio","command":"npx","args":["-y","antics-mcp"]}'Install antics MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"antics-mcp": {
"command": "npx",
"args": [
"-y",
"antics-mcp"
]
}
}
}Install antics MCP in Codex
$ codex mcp add antics-mcp -- npx -y antics-mcpInstall antics MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.antics-mcp] command = "npx" args = ["-y", "antics-mcp"]
Install antics MCP in Gemini CLI
$ gemini mcp add -s user antics-mcp npx -- -y antics-mcpInstall antics MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"antics-mcp": {
"command": "npx",
"args": [
"-y",
"antics-mcp"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachableantics-gg/antics-mcp is public and reachablegithub.com/antics-gg/antics-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-09-29github.com/antics-gg/antics-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from antics-mcpPass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubantics-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-mcp
Claude 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.
Tools
| Tool | What it does | Login? |
|---|---|---|
deploy_game |
Deploy a game (html for a single file, or files for a multi-file project) → returns a playable multiplayer URL. Keyless (ephemeral room) unless given a projectId. |
No |
create_project |
Create a project; returns its id, publishable key (pk_), and secret key (sk_, shown once). |
Yes |
get_leaderboard |
Read a project's leaderboard (top scores). | Yes |
list_projects |
List your projects. | Yes |
set_share_preview |
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.
antics MCP questions
How do I add antics MCP to Claude Code?
Run claude mcp add antics-mcp -- npx -y antics-mcp in your terminal. Add --scope user to make it available in every project.
How do I add antics MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Do I need to log in to deploy a game?
No, you can use the deploy_game tool without any login to create ephemeral, keyless URLs that last 24 hours.
How many players can join a room?
Ephemeral rooms created without a project ID can hold up to 8 players.