Gamealia
Official# Gamealia MCP server
Publish your web game on [Gamealia](https://gamealia.app) from your AI coding assistant, and keep
**60–70% of the ad revenue** (100% from the players you bring), with **no exclusivity**.
Tell Claude Code, Cursor, Codex, VS Code, Gemini CLI, Windsurf, Cline, Zed or Claude Desktop:
> Publish this game on Gamealia. It's in ./my-game.
The server analyzes the project, integrates the Gamealia SDK (or swaps Poki / CrazyGames calls
through the compatibility layers), builds it, tests it in a real browser on desktop and mobile,
writes the listing and the cover, uploads the build and submits it for review **after you
confirm**. You approve one sign-in in your browser. A person reviews every version before it goes
live.
Works with any engine that exports to the web: plain HTML5 and JavaScript, Phaser, PixiJS,
three.js, Unity WebGL, Godot, GameMaker, Construct.
## Install
Node.js 22 or newer.
```sh
# Claude Code
claude mcp add gamealia -- npx -y gamealia-mcp
```
Any other MCP client (stdio):
```json
{
"mcpServers": {
"gamealia": { "command": "npx", "args": ["-y", "gamealia-mcp"] }
}
}
```
The local autotest, preview and cover tools also use `playwright-core` with a headless Chromium
(`npx playwright-core install chromium`).
Ready-made skills and configs for each assistant:
[gamealia.app/developers](https://gamealia.app/developers#mcp).
## Tools
| Tool | What it does |
|---|---|
| `gamealia_analyze_project` | Detects the engine, the build and what the game needs |
| `gamealia_integrate_sdk` | Adds the SDK and lifecycle calls, or migrates Poki / CrazyGames calls |
| `gamealia_run_autotest` | Runs the game in a headless browser, desktop and mobile, with screenshots |
| `gamealia_create_game` | Creates the game page: title, description, controls, cover, translations |
| `gamealia_upload_version` | Uploads the build and submits it for review |
| `gamealia_get_status` | Review state and live version |
| `gamealia_get_earnings` | Estimated and confirmed earnings |
| `gamealia_playtest` | Plays the game in a browser and reports what it sees |
Full reference: [Publish with AI](https://gamealia.app/docs/publishing-with-ai).
## The deal for developers
- 60% of your game's ad revenue; launch partners (first game live by December 31, 2026) get 70%
on all their games until June 30, 2027.
- 100% of the ads seen by players who arrive through your own link.
- Monthly payouts once your balance passes USD 50: PayPal, Payoneer, Wise or Mercado Pago.
- No exclusivity: keep your game on Poki, CrazyGames, itch.io or your own site.
More: [gamealia.app/developers](https://gamealia.app/developers) ·
[Revenue and payouts](https://gamealia.app/docs/revenue-and-payouts) ·
[Migrate from Poki](https://gamealia.app/docs/migrate-from-poki) ·
[Migrate from CrazyGames](https://gamealia.app/docs/migrate-from-crazygames)
## Contact
hello@gamealia.app
TDQS
Scored across 26 tools
Tools cluster into clear phases (local dev, account, listing, publishing, analytics) and descriptions explicitly cross-reference the right sibling, e.g. preview vs playtest vs run_autotest. A few pairs still brush against each other — analyze_project vs check_integration (both static inspection), get_status vs list_versions (both report version state) — but the descriptions disambiguate with 'use X for Y, Z for W' guidance.
Every tool is snake_case with a uniform gamealia_ prefix and most follow verb_noun (create_game, upload_version, list_versions, get_stats). Minor deviations exist: bare-domain names like gamealia_accounts, gamealia_whoami, gamealia_build, plus a playtest_/playtest_act/playtest_stop sub-family that breaks strict verb_noun but is internally readable.
26 tools is slightly heavy, but the surface maps a genuinely multi-stage pipeline (analyze → integrate → check → autotest → playtest → listing → upload → submit → stats), so nearly every tool has a distinct job. Only playtest/playtest_act/playtest_stop and the autotest trio inflate the count for a single function.
Happy-path lifecycle is well covered from SDK integration through review and earnings, but lifecycle dead ends remain: no delete/archive/unpublish for games or versions, no accept/decline for the pending invites that gamealia_accounts surfaces, and no way to see a single game's full listing text/edit stats beyond what get_status texts:true gives. Agents can mostly work around these, but they are real gaps for a publishing platform.