# neme.world > neme.world is a home for web games: a player opens a link and plays, on a phone or a computer, with nothing to install. A game is a folder of static files. This page tells a coding agent how to build one that works here and how to publish it. ## What a game must be - Static files with an HTML entry page (`index.html` unless neme.json says otherwise). No server of its own, no build step on our side: publish what your build produced. - Self-contained. It is served from its own origin (https://.neme.world) under a path that changes with every version, so refer to your own files with relative URLs (`./game.js`, not `/game.js`). - Playable with what the player has. Say which of keyboard, mouse, touch and gamepad it supports; a game that works with touch reaches phones. - At most 5,000 files, 95 MB per file and 1024 MB per version. Hidden files and node_modules are never uploaded. - No service worker: a game cannot install one here, and must work without it. - Original. Working in a familiar genre is fine; recreating a specific existing game, or using its name, characters, art or music, is not. Third-party art, audio and code need a license that allows it, with credit. Starting from nothing? https://github.com/coderneme/neme-starter is a small complete game that already works here, with a `neme.json` and these instructions beside it: copy it and change it. ## Publish 1. The developer signs up at https://neme.world/signup (anyone can), confirms their email address from the link they are sent, creates an API token at https://neme.world/dashboard and sets it as NEME_TOKEN. Never ask for it in chat or write it into a file. A publish that answers "Confirm your email address" means that step is still to do; only the developer can do it. 2. Describe the game in `neme.json`, next to the project (`npx neme-world init` writes a first one): ```json { "slug": "my-game", "title": "My Game", "description": "One or two sentences players will see.", "tags": ["arcade"], "dir": "dist", "cover": "cover.png", "controls": ["keyboard", "mouse", "touch"], "aspect": "16:9", "leaderboard": { "max": 5000 } } ``` `dir` is the folder holding the built entry page. `cover` is an image inside it (leave it out and a screenshot is taken). `aspect` is one of 16:9, 4:3, 1:1, 3:4, 9:16. `leaderboard` is optional: `max` is the highest score a player could really reach. For an open-source game add `license`, `sourceUrl` and `credit`. To show the game on the developer's own website, add `"embedOn": ["example.com"]` (their site's host names, at most five) and put `` on a page there; no other site can embed it, and plays there are counted in the same dashboard. 3. Upload without going live, and give the developer the link it prints: ```sh npx neme-world publish --preview ``` 4. When they say it is ready, make it live: `npx neme-world promote `, or `npx neme-world publish` to upload and go live in one step. Every publish is a new version; any earlier one can be made live again. A game keeps at most 200 versions: when it is full, `npx neme-world versions` lists them and `npx neme-world delete ` deletes one for good (ask the developer which; the one players are on cannot be deleted). 5. Tell the developer where it is: a live game plays at once at https://neme.world/g/, a link they can share. It appears on neme.world's home page and in search after the platform has looked at the developer's first game (usually within a few days); their later games appear at once. Nothing more needs doing for that. ## As tools (MCP) The same commands are available to an agent as tools. Add this server to your agent's MCP settings: ```json { "mcpServers": { "neme": { "command": "npx", "args": ["-y", "neme-world", "mcp"], "env": { "NEME_TOKEN": "" } } } } ``` Tools: `neme_guide` (this page), `neme_init`, `neme_publish` (with `preview`), `neme_promote`, `neme_versions`, `neme_delete_version`, `neme_metrics`. ## Talk to the player (optional SDK) Include `` in the entry page. Outside neme.world every call does nothing, so one build works everywhere. - `window.neme?.ready()` once the game can be played. - `window.neme?.score(1280)` at the end of a run. The page's Share button then carries the player's best as a challenge link, and if the game has a leaderboard a new best is offered to it under a made-up name. - `window.neme?.event('level_complete', 3)` for anything else worth counting. - `window.neme?.share()` from a tap or click, to open the share sheet from a button of your own. - If the game draws on a ``, players get a Record clip button with nothing more to do; `window.neme?.clip.start()` and `.stop()` do the same from your own button. If a command here does not do what this page says, the developer can report it at https://github.com/coderneme/neme-cli/issues. ## API Authenticate with `Authorization: Bearer $NEME_TOKEN`. - `PUT https://neme.world/api/v1/games/:slug` create or update details (JSON, the neme.json fields) - `POST https://neme.world/api/v1/games/:slug/versions` upload a zip (`?activate=0` for a preview) - `POST https://neme.world/api/v1/games/:slug/activate` `{"version": 3}` to make a version live, `null` to unpublish - `DELETE https://neme.world/api/v1/games/:slug/versions/:n` delete a version that is not live - `GET https://neme.world/api/v1/games/:slug/metrics` the numbers behind the dashboard More for people: https://neme.world/developers