A lot of web games are now built with an AI coding assistant. The odd part is the last step: you finish the game in Claude Code or Cursor, then leave the chat to zip a build, fill in a portal form, write a description, take screenshots and wait for a review email.
With the Model Context Protocol (MCP) the assistant can do that last step too. This post shows how it works with Gamealia's MCP server (disclosure: I'm on the Gamealia team), what the assistant actually does, and which parts stay human.
Which assistants
The server is a normal stdio MCP server published on npm as gamealia-mcp (MIT). It works with anything that speaks MCP:
| Assistant | Setup |
|---|---|
| Claude Code (terminal, VS Code, JetBrains) | claude mcp add gamealia -- npx -y gamealia-mcp |
| Codex / ChatGPT (CLI, IDE extension, app) | codex mcp add gamealia -- npx -y gamealia-mcp |
| Cursor (editor and CLI) |
~/.cursor/mcp.json → "gamealia": {"command": "npx", "args": ["-y", "gamealia-mcp"]}
|
| Gemini CLI / Gemini Code Assist |
~/.gemini/settings.json, same mcpServers entry |
| Kimi Code |
~/.kimi-code/mcp.json, same entry, or /mcp-config
|
| VS Code (Copilot), Windsurf, Cline, Zed, opencode | their MCP settings file |
Or install the CLI and let it set up every assistant it finds: gamealia agents install.
What you say
Publish this game on Gamealia.
That's the whole prompt. Behind it the assistant:
- Inspects the project: engine (plain JS, Phaser, PixiJS, three.js, Unity WebGL, Godot, Construct...), the build folder, the entry file.
-
Adds the SDK: one script tag plus lifecycle calls (
loadingStop,gameplayStart/gameplayStop, pause and mute for ads). If the game already calls the Poki or CrazyGames SDK, those calls keep working through compatibility layers, so the diff is small. - Runs a browser test on desktop and mobile profiles: does it load, does the SDK start, does it react to input, does it pause when asked, any console errors or blocked network calls. Every finding comes back as a warning with the exact fix (file, line, call to add), and the assistant applies it.
- Writes the listing: title, description, controls, tags. Gamealia translates it into 32 languages, so the game page exists in Spanish, Portuguese, Japanese, Arabic and so on.
- Uploads the build and submits it for review.
Sign-in is a one-time device code in the browser: no password or API key is pasted into the chat.
What stays human
- Review. A person plays every version before it goes live. The automatic test only fails a build on deterministic checks (it loads, the SDK starts); everything subjective is a warning.
- Your decisions. The assistant asks before submitting, and you can stop at "upload and test" to look at the preview yourself.
The terms, plainly
- 60% of ad revenue to the developer (70% for launch partners who publish their first game before the end of 2026, until June 2027), and 100% of the ads seen by players you bring through your own link.
- No exclusivity: keep the same game on CrazyGames, itch.io or your own site.
- Ads are not live yet (the ad network approval is in progress), so nothing has been paid out so far. If you publish now, you get the listing, the players and the tooling; revenue starts when ads do.
Try it
- Docs: https://gamealia.app/docs/publishing-with-ai
- Developer page: https://gamealia.app/developers
- Source of the MCP server: https://github.com/gamealia/gamealia-mcp
Questions or rough edges: hello@gamealia.app.
Top comments (0)