Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"antics": {
"args": [
"-y",
"antics-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'antics-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked antics-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
A Unified MCP Server Management App (MCP Manager).
MCP Server for kubernetes management commands
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
MCP Security Weekly
Get CVE alerts and security updates for io.github.antics-gg/antics-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
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.
| 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 |
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.
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.