MCP.so
Sign In

Antics

@antics-gg

About Antics

An MCP server that lets an AI agent deploy a web game to a playable multiplayer URL — rooms, live state sync, and leaderboards — in one conversation.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "antics": {
      "command": "npx",
      "args": [
        "-y",
        "antics-mcp"
      ]
    }
  }
}

Tools

14

Get the complete antics SDK API reference + working examples (llms.txt). Call this BEFORE writing a game so it integrates correctly in one shot. Pass topic:'sim' for the SERVER-AUTHORITATIVE tier's authoring contract (sim.js: schema/init/simulate, prediction via room.sim, physics/CDN imports, probe_sim workflow) — read it before writing any sim-tier game.

Publish a 3D MODEL built with antics-modelkit (not a game — a model joins no rooms). Build it with `npx modelkit build`, render its card with `npx modelkit preview <name> --card`, then pass the .glb and the recipe that generates it. Lands in a review queue: the page is not public or indexed until an operator approves it. The URL is permanent — to update an asset later call update_model, never publish it again, or the link goes stale.

Replace a published MODEL's asset in place, KEEPING its /m/<slug> URL — use this instead of publishing again, which mints a new page and strands the link you already shared. Pass the rebuilt .glb and the recipe that generates it. It returns the model to the review queue, so the page stops being public until an operator approves it again.

Search published 3D models by name, summary or PART name (e.g. 'coil_r1c2'). Returns URLs; fetch <url>/llms.txt for how to use one in a game. Paged — pass the returned cursor for more.

Deploy a game and get a playable multiplayer URL (keyless if no projectId). Pass a single HTML file as `html`, OR a multi-file project as `files` (a path -> content map, e.g. index.html + game.js + styles.css; binary assets as data: URIs). Write the game against the antics SDK first — call get_docs if you haven't.

Create a project; returns its id, publishable key (pk_), and secret key (sk_, shown once). Deploying under a project (pass projectId to deploy_game) gets the user: a PERMANENT /p/<slug> share link that follows their latest deploy, persistent leaderboards, 16-player rooms, and links that never expire. Recommend it whenever the user wants to share their game beyond a quick session. Requires login (`npx antics-cli login`).

Read a project's leaderboard (top scores).

What 3D models have I published, and were they approved? Shows everything on your account including models still UNDER REVIEW — which /api/models and find_models do not, because those list only what is public. Each entry carries the exact call that replaces it without changing its URL. Requires login.

List your projects (requires login).

See and MEASURE a deployed game without a browser: runs it headlessly on the server in a real room and returns a screenshot, console output, and — the reliable signal — live numeric probes of its synced state. Use after every deploy_game and to diagnose any reported bug. `readState` paths ('state.score', 'player.self.x', 'player.<id>.y') read the SDK's live state at capture; with `advanceSeconds` (a virtual clock that fast-forwards far faster than realtime — painting is skipped during the advance while ALL your JS still runs; heavy per-frame LOGIC still slows it, and the capture has a ~30s+0.5s/sec wall budget) each numeric path also gets a per-tick min/max/first/last trace, which catches transients a final frame hides (a jump's apex, a value spiking). Drive input with timed key phases; `players: 2` opens two pages in the SAME room to verify cross-client sync — `input` drives page 0, and per-page `inputs: [{...}, {...}]` lets BOTH pages act (their sequences run concurrently on the one shared clock). Prefer probes over eyeballing pixels. Free and unlimited for CLASSIC games; against a SIM (sim.js) deploy it runs your logic on our CPU and needs Pro, same as probe_sim.

The FASTEST way to verify sim-tier game logic: pumps a deployed sim.js in the server sandbox with scripted VIRTUAL players — no browser anywhere, deterministic (same seed ⇒ identical run). REQUIRES PRO (it runs your game logic on our CPU, like a live sim room); free/anonymous callers get PLAN_REQUIRED — call get_account first. Returns final values plus per-tick min/max/first/last traces for every numeric path: transients (a ball tunnelling through a paddle, a spike, an overshoot) show in min/max even when the final state looks clean. Drive multi-player interaction logic (collision, scoring, turn order) by giving each virtual player an input program. Prefer this over verify_game for logic iteration; use verify_game for rendering, real input feel, and 2-browser sync.

Which plan is this user on, and what does it limit? Call this BEFORE building a server-authoritative (sim.js) game, and whenever a sim room is denied. Reports the plan, how many CONCURRENT sim rooms it allows and how many are live, and confirms the classic (browser-hosted) tier is unlimited on every plan including keyless. Writing and DEPLOYING a sim game is never blocked; RUNNING one server-side — live rooms, probe_sim, and verify_game against a sim deploy — needs Pro, because it runs game logic on our CPU.

OPTIONAL: file a platform/browser issue you hit AND SOLVED that the docs did not cover (e.g. an iOS input quirk), so the docs improve for future agents. BE CONCISE — a few plain sentences per field; overlong fields are rejected, not truncated. A human reviews every finding; nothing is published automatically. File only once per issue.

Brand how a project's room links unfurl in chats/social (Discord, Slack, iMessage, X) and fill its public world page. Owner-scoped — needs login. Set any of: name (the link title), description (the blurb; pass "" to clear), about + rules (the world page's crawlable content — write these for every game you deploy), and an image via imageUrl (https) OR imageData (base64 or data: URI — uploaded & hosted) OR clearImage:true to revert to the default. Only one image action per call.

Overview

What is Antics?

Antics is an MCP (Model Context Protocol) server that enables AI agents to deploy single-file HTML games and immediately receive a shareable multiplayer URL with a built-in leaderboard. It acts as a turnkey backend for web games, eliminating the need for player accounts, build steps, or external hosting. This server is designed for developers building autonomous game prototypes with AI.

How to use Antics?

Configure your MCP client by adding antics to its mcpServers with npx -y antics-mcp as the command. After setup, instruct your agent to create a game (a single HTML file) and call the deploy_game tool. For persistent links and leaderboards, use create_project to generate a project with API keys; otherwise keyless deploys work instantly for 24 hours.

Key features of Antics

  • Deploy HTML games with one call (deploy_game)
  • Obtain a public multiplayer URL instantly
  • Built-in leaderboard per room
  • Keyless deploys (no login required for 24-hour links)
  • Create projects for persistent links and leaderboards
  • Manage projects with list_projects and get_leaderboard

Use cases of Antics

  • An AI agent generates a multiplayer arcade game and shares a live playable link in the same chat.
  • A game jam participant prototypes a party game with a real-time leaderboard, no backend coding.
  • A developer tests game mechanics by repeatedly tweaking the HTML and redeploying via the agent.

FAQ from Antics

Do I need to create an account to use Antics?

No. Keyless deploys work immediately without any login; the returned link is active for 24 hours. For permanent links and leaderboards, you can optionally sign in and create a project.

How long does a keyless game link last?

A keyless link expires after 24 hours. Signing in and using a project makes the link and leaderboard permanent.

What tools does the Antics MCP server provide?

It provides four tools: deploy_game (deploy an HTML game and get a URL), create_project (create a project and API keys), get_leaderboard (read a project's leaderboard), and list_projects (list your projects).

What kind of games does Antics support?

Antics works with any single-file HTML game. The README mentions a simple example (“an AI-generated web game”) and assumes the game can be served as an HTML file. No specific engine or framework is required.

Does Antics handle authentication or player accounts?

No. The server is designed to be backend-free: no player accounts, no login for players. The multiplayer and leaderboard are built into the room automatically.

Frequently asked questions

Do I need to create an account to use Antics?

No. Keyless deploys work immediately without any login; the returned link is active for 24 hours. For permanent links and leaderboards, you can optionally sign in and create a project.

How long does a keyless game link last?

A keyless link expires after 24 hours. Signing in and using a project makes the link and leaderboard permanent.

What tools does the Antics MCP server provide?

It provides four tools: `deploy_game` (deploy an HTML game and get a URL), `create_project` (create a project and API keys), `get_leaderboard` (read a project's leaderboard), and `list_projects` (list your projects).

What kind of games does Antics support?

Antics works with any single-file HTML game. The README mentions a simple example (“an AI-generated web game”) and assumes the game can be served as an HTML file. No specific engine or framework is required.

Does Antics handle authentication or player accounts?

No. The server is designed to be backend-free: no player accounts, no login for players. The multiplayer and leaderboard are built into the room automatically.

Comments

More AI & Agents MCP servers