Neme World
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
neme-world
Publish a web game to neme.world from the command line.
If your game runs in a browser tab from static files, it runs on neme.world: any engine, any framework, hand-written or AI-assisted. You keep your own site; neme.world is one more place people can find and play it.
npx neme-world init # writes neme.json
npx neme-world publish # uploads your build and puts it liveBefore you publish
Create an account at neme.world. Anyone can; there is no waiting list. Confirm your email address from the link you are sent, then make an API token in your dashboard.
Put the token in your environment:
export NEME_TOKEN=neme_…Build your game the way you normally do.
Your game is live at its own link the moment you publish it. It joins neme.world's home page and search once we have looked at your first game; your later games appear at once.
Related MCP server: hypercho-games-publisher
neme.json
{
"slug": "my-game",
"title": "My Game",
"description": "One or two sentences players will see.",
"tags": ["arcade"],
"dir": "dist",
"cover": "cover.png"
}Field | Meaning |
| The game's address: |
| Shown to players. |
| Shown on the game's page and in link previews. |
| Up to 8, used for browsing. |
| Folder holding your built |
| The HTML file to open, if it isn't |
| An image inside |
| Shape of the game on its page: |
| What the game plays with: any of |
| Optional, for open-source games and attribution. |
What publish does
It uploads dir file by file as a new version, which goes live at once. Only files that changed since your last
publish are sent, so updating a large game is quick. Hidden files (anything starting with a dot) and
node_modules are never uploaded. Every version is kept, and you can make any earlier one live again from your
dashboard.
A single file can be up to 95 MB, and a game up to 1 GB. One publish per game runs at a time: starting a second replaces the first.
Previews
npx neme-world publish --preview # uploads the build, prints a link to try it; players are not affected
npx neme-world promote 7 # makes version 7 livepromote also takes you back to an earlier version.
Options
Installed (npm i -D neme-world), the command is simply neme.
neme publish [dir] Publish the game described by dir/neme.json (default: current folder)
neme init [dir] Create a neme.json
neme promote <n> [dir] Make version n live
--preview Upload without going live
--token <token> API token (default: $NEME_TOKEN)
--api <url> Platform address (default: $NEME_API or https://neme.world)In CI
- run: npm run build
- run: npx neme-world publish
env:
NEME_TOKEN: ${{ secrets.NEME_TOKEN }}Talking to the player
To report load time, scores and your own events to your dashboard, see the SDK section of the developer guide.
MIT licensed.
Versions
A game keeps a limited number of versions (200). neme versions lists them and says which one players are on;
neme delete 3 deletes version 3 for good. The version players are on cannot be deleted: make another live first.
For coding agents
neme mcp runs the same commands as tools for an AI coding agent, over the Model Context Protocol. Add it to
your agent's MCP servers:
{ "mcpServers": { "neme": { "command": "npx", "args": ["-y", "neme-world", "mcp"], "env": { "NEME_TOKEN": "neme_…" } } } }Tools: neme_guide (how to make a game that works on neme.world), neme_init, neme_publish (with preview),
neme_promote, neme_versions, neme_delete_version and neme_metrics. The agent is told to upload a preview, show you the link, and make a version
live only when you say so. The guide it reads is also at https://neme.world/llms.txt.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build a playable game with your coding agent and publish it on Sekai in one step.
Publish web games on Gamealia from AI assistants: SDK, autotest, listing, upload. Local or remote.
Publish, test and share browser games on PlayDrop from your AI agent.
Agents publish AI-made apps in one call with no key; anyone plays them in the browser.
Related MCP Servers
FlicenseAqualityDmaintenanceEnables AI agents to deploy multiplayer web games as playable URLs with rooms, live state sync, and leaderboards, all through a single tool call.45-- AlicenseNot gradedqualityBmaintenanceEnables AI agents to validate and publish game bundles to the Hypercho Games marketplace, including uploading browser builds, banners, screenshots, and metadata.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to upload, share, preview, and publish a generated HTML page from an agent, returning a stable link and version link after browser-authorized access.15 npmMIT No Attribution
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to publish and manage HTML5 browser games, giving each game its own address and catalogue page with leaderboards, cloud saves, player clips, daily stats, versioning, and rollback.1MIT