A new tool lets AI coding assistants publish your browser game for you

The last step of making a game

Plenty of browser games are now built with an AI coding assistant. But the finish line still tends to pull you out of the assistant: you package the build, fill in a portal's submission form, write a description, capture screenshots and then wait on an email from a reviewer.

As dev.to reported in a post by a member of the Gamealia team (who discloses that affiliation), a standard called MCP can hand that whole routine to the assistant. MCP, the Model Context Protocol, is a common way for AI tools to plug into outside services. Gamealia is a web game portal, and it publishes an MCP server called gamealia-mcp on npm under an MIT open-source license.

What happens after one sentence

The only instruction the post says you need is to ask the assistant to publish the game on Gamealia. From there, the assistant works through a list of jobs.

• Looks over the project. It identifies the engine (plain JavaScript, Phaser, PixiJS, three.js, Unity WebGL, Godot or Construct, among others), the build folder and the entry file.
• Adds the platform's SDK. An SDK is a small code package that lets a game talk to a platform. Here it means one script tag plus calls that signal when loading ends, when play starts or stops, and when to pause or mute for ads.
• Tests the game. A browser check runs on desktop and mobile profiles. It looks at whether the game loads, whether the SDK starts, whether it responds to input and pauses on request, and whether there are console errors or blocked network calls.
• Fixes what it finds. Each problem comes back as a warning naming the file, line and call to change, and the assistant applies the fix.
• Writes the listing. That covers title, description, controls and tags, which the platform then translates into 32 languages.
• Uploads and submits.

If your game already uses the Poki or CrazyGames SDKs, the post says those calls keep working through compatibility layers, so the code changes stay small.

Setup and safety

The server works with any assistant that speaks MCP. The post gives one-line setup commands for Claude Code and Codex, config-file entries for Cursor, Gemini CLI and Kimi Code, and points VS Code with Copilot, Windsurf, Cline, Zed and opencode to their own MCP settings files. A separate command-line tool can also detect the assistants on your machine and configure them all.

On security, sign-in happens through a one-time device code in your browser. That means you never paste a password or API key into the chat, which is where such secrets can leak or get logged.

What people still decide

Automation stops short of the final call. According to the post, a person plays each version before it is published. The automated test only blocks a build on strict yes-or-no checks, such as whether the game loads and the SDK starts. Anything that is a matter of judgment shows up as a warning instead.

You keep control too. The assistant asks before it submits, and you can pause after the upload and test stage to try the preview yourself.

The money, and the catch

The post says developers get 60% of ad revenue. Early partners whose first game goes up before 2026 ends get 70%, a rate that lasts until June 2027. Ads from players you bring in through your own link pay out at 100%. There is no exclusivity, so the same game can stay on CrazyGames, itch.io or your own site.

The important caveat is that ads are not running yet, because the ad network's approval is still in progress. Nothing has been paid out so far. Publishing now gets you a listing, players and the tooling, with revenue only starting once ads switch on.

Also keep in mind that the author works for the platform, so this is a vendor walkthrough rather than an independent test. The details above are the vendor's own claims.