klyo games MCP server: publish HTML5 games from Claude, ChatGPT, Cursor, VS Code, Codex or Gemini CLI

Publish a browser game straight from your AI assistant. Upload a ZIP, or point at a game that already runs somewhere else, and the game gets its own address g-<name>.klyo.pl, a page in the klyo games catalogue, leaderboards, cloud saves, clips recorded by players and daily stats. Publishing is free, there is no exclusivity and you keep the rights.

MCP (Model Context Protocol) is the open standard assistants use to call outside tools. This repository documents the hosted klyo server and ships ready-made packages for Claude Code, Gemini CLI and any agent that reads skills. There is nothing to run on your side.

Documentation

The product documentation lives in docs/. It is generated from the website, so every file names its canonical page:

• Everything klyo games can do: every feature of the portal, grouped by area, each one checked against our code when the site is built.
• klyo Developer Studio: upload, a preview on four screens, versions and rollback, statistics, the creator page.
• klyo SDK reference and the MCP server.
• Help center: publish an HTML5 game, release a new version or roll back, add a leaderboard, fix a white screen, record a gameplay clip with captions.
• Po polsku: spis dokumentacji.

Server

The first tool call opens the klyo sign-in page; signing in with Google or with a one-time e-mail link creates the account on the spot. One step cannot be automated: the account owner accepts the developer terms once, in a browser, at https://dev.klyo.pl/.

Connect

Claude Code, as a plugin (the server plus a skill that walks the agent through build, local test, upload and release):

/plugin marketplace add krastranseu-lang/klyo-games-mcp
/plugin install klyo-games@klyo

Claude Code, server only

claude mcp add --transport http klyo-games "https://panel.klyo.pl/mcp?profil=gry"

Codex CLI

codex mcp add klyo-games --url "https://panel.klyo.pl/mcp?profil=gry"
codex mcp login klyo-games

Gemini CLI, as an extension (server plus skill), then sign in once with /mcp auth klyo-games:

gemini extensions install https://github.com/krastranseu-lang/klyo-games-mcp

Any agent that reads skills (Claude Code, Codex, Cursor, Gemini CLI, Copilot and others, through skills.sh):

npx skills add krastranseu-lang/klyo-games-mcp

The skill tells the agent when and how to use klyo. It still needs the server connected.

Claude (claude.ai, desktop, mobile): Settings → Customize → Connectors → + → Add custom connector → paste the URL → Add (leave Client ID and Secret empty) → sign in → Allow. The connector then appears on your phone as well.

ChatGPT (paid plan with Developer mode): Settings → Apps & Connectors → Advanced → Developer mode → Create → paste the URL → finish signing in in the pop-up.

Cursor: use the button above, or ~/.cursor/mcp.json:

{ "mcpServers": { "klyo-games": { "type": "http", "url": "https://panel.klyo.pl/mcp?profil=gry" } } }

VS Code: use the button above, or .vscode/mcp.json, then click Auth above the entry:

{ "servers": { "klyo-games": { "type": "http", "url": "https://panel.klyo.pl/mcp?profil=gry" } } }

opencode, opencode.json:

{ "mcp": { "klyo-games": { "type": "remote", "url": "https://panel.klyo.pl/mcp?profil=gry", "enabled": true } } }

Your own script or CI step: generate a key in the studio at https://dev.klyo.pl/ ("Server integration (API)") and send Authorization: Bearer klyo_sk_… to the same URL. The same tools, no login window.

Then just say: "publish this game on klyo, the package is in this folder".

Tools

The table below is generated from the live server (tools/list, checked on 23 September 2026). Anyone can list the tools without signing in; every call needs sign-in.

What happens when you publish

1. The assistant reads the production standard (klyo_game_requirements), builds or keeps your game, and runs the local test klyo-test.mjs. The server runs the same file after upload.
2. The package is checked (size, files, third-party ads, malicious code, other companies' brands) and measured on four screens.
3. The game goes live at https://g-<name>.klyo.pl in a waiting state. You play it and press Release to the catalogue in the studio. The assistant cannot press that button for you.
4. New versions go to a preview first; players keep the old version until you release the new one, and the previous version stays available for a one-step rollback.

How it compares

Checked on 23 September 2026 in each service's own documentation. Those services change their rules without notice; open an issue if something no longer matches.

What is live and what is not

• Publishing is free and immediate. After the automatic check you play your own game in a preview and release it with one click. A person from klyo looks at it after that; until then the game is visible only to adult accounts.
• Revenue share: 70% of the net ad revenue attributed to your game, payout threshold 100 PLN. It starts the day Google AdSense approves the portal. As of today no ads are shown and nothing has been paid out yet.
• Leaderboards receive scores from the game itself over a signed round, never typed in.
• The portal is new. It does not have the traffic of a big portal yet, and we do not pretend it does.

Privacy

The server stores what you publish (game files, texts, stats) and your account, and it keeps an audit log of every change made through these tools. klyo runs no AI model for your assistant: translations and texts are written by your own assistant on your own plan. Full policy: https://games.klyo.pl/privacy/. Developer terms: https://games.klyo.pl/developer-terms/.

Links