Antics Mcp

io.github.antics-ggPublished by GitHub account antics-ggv0.5.1Updated Oct 24, 2026

Deploy a web game to a playable multiplayer URL with rooms, state sync, and leaderboards.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an AI assistant deploy a web game it wrote to a playable multiplayer URL with rooms, live state sync and leaderboards.

What you can do
Deploy a single-file or multi-file web game and get back a playable multiplayer URL, keyless and ephemeral unless a project is given. Create projects and list them, receiving a publishable key and a secret key shown once. Read a project's leaderboard top scores. Set the title, description and image used when a project's room links unfurl on social media.
When to use it
Use it when an assistant writes a browser game and you want friends to play it together without building a backend or setting up player accounts. Useful for quick multiplayer prototypes and shareable demos.
Requirements
Runs locally over stdio via npx, so Node.js and network access are needed. No login is required for keyless ephemeral deploys; owner-scoped tools need a one-time sign-in with the antics-cli login command using GitHub.
Before you install
create_project returns a secret key shown only once, so store it carefully. Deploying publishes a game to a public URL that anyone with the link can open. Keyless rooms are limited to 8 players and expire after 24 hours; persistent links and leaderboards require signing in.

Installation

In SourceWeft

  1. Open Antics Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

sh
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.):

json
{  "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

ToolWhat it doesLogin?
deploy_gameDeploy 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_projectCreate a project; returns its id, publishable key (pk_), and secret key (sk_, shown once).Yes
get_leaderboardRead a project's leaderboard (top scores).Yes
list_projectsList your projects.Yes
set_share_previewBrand 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

Source: README.md at commit bd6433a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.5.1LatestSep 29, 2026
  2. v0.5.0Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.