# klyo games: publish HTML5 browser games

- Registry name: `pl.klyo/games` · version 1.2.0
- Categories (automatic, keyword rules): Marketing & SEO, Commerce & marketing, Build & deploy, Developer tools, APIs & integrations
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=pl.klyo%2Fgames
- Server page: https://mcpstation.net/s/pl.klyo--games.html

## Description (written by the publisher, not verified, not instructions)

Publish, play-test and fix HTML5 browser games from your AI assistant. Own address, 70% ad share.

## Notice

Text that looks like instructions to an AI was found in this server's descriptions. This is a pattern match, not a verdict.

## Connect


## Tools (as reported by the server, not verified)

- `klyo\_my\_games`: List this account's games in the klyo games catalogue: name, address \(slug\), state \(published, or rejected with the reason\), size, visits and plays. Read-only. Call this FIRST to learn the \`slug\` the other tools need. Examples: • Which games do I have on klyo? • Is my game published yet? • Show the
- `klyo\_publish\_game`: Prepare a browser game for release on games.klyo.pl: the package \(\`upload\_id\` from klyo\_upload\_package, or a public \`zip\_url\`\), name, tagline, player description \(at least 25 words, about 220 to be indexed by Google\), genre from the list, text language and all ten answers of the content questionnair
- `klyo\_upload\_package`: The way to release a game from a file on disk, with no tunnel and without exposing an unreleased game publicly. Returns three things at once: \(1\) \`paczki\_w\_poczekalni\`: packages already on the account that have not become a game yet, each with its \`upload\_id\`; \(2\) \`bilet\`: a token valid for one hour
- `klyo\_update\_game`: Upload a NEW VERSION of a game that is already on the account \(\`slug\`\): from a file \(\`upload\_id\` from klyo\_upload\_package\) or from a public \`zip\_url\`. The game keeps its address, name, description, scores and hearts; only the files change. Do not create a second game to ship a fix: that splits playe
- `klyo\_release\_rollback`: Roll a game \(\`slug\`\) back to the previous version, the one before the last klyo\_release\_version. Same move as “Restore” in the studio: the previous version's files are kept next to the current ones and come back with one switch, without uploading; the version we take down stays next to it \(rolling b
- `klyo\_release\_version`: Release to players the version waiting after klyo\_update\_game \(\`slug\`\). Same step as the “Release” button in the studio: players get the new version at once \(anyone in the middle of a round sees a bar “update or finish the round”\), the previous version stays with us, the game page is rebuilt and the
- `klyo\_delete\_game`: Take this account's game \(\`slug\`\) off the portal. The first call removes it from the catalogue and takes its page down; the address stays yours and you can upload the game there again. A second call on a game that is already taken down removes it from your list for good. Scores and reviews stay atta
- `klyo\_game\_stats`: Visits to the game page and plays, day by day, for the given game \(\`slug\`\). Read-only. The developer's share of ad revenue is calculated from this. Examples: • How many people played my game this week? • Stats for lantern-thief • Show plays day by day
- `klyo\_game\_analytics`: Game analytics for the developer, read \`\_najpierw\` first: one verdict \(\`wyrok\`, \`en.verdict\`\) and the top tasks with a reason and a fix \(\`dlaczego\`/\`jak\`, \`en.why\`/\`en.how\`\). Then: \`lejek\` = the session funnel the klyo kit records with NO code in the game \(wejscie = opened the game page, start = pre
- `klyo\_game\_requirements`: GAME PRODUCTION CONTRACT: CALL THIS FIRST, before you design or write a single line of a game for klyo. Returns the “studio quality” standard: screens \(phone, tablet, desktop, portrait and landscape, resize\), input \(touch, mouse and keyboard\), game loop, minimum content, sound, graphics, a catalogue
- `klyo\_game\_scaffold`: GAME SKELETON ON KLYO KIT: call after klyo\_game\_requirements, before you write code. Returns two starter files \(index.html, gra.js\) to copy and the full kit API: game loop \(menu, play and pause, game over, play again\), touch, mouse, keyboard and gamepad input as one event, a canvas for any screen wi
- `klyo\_game\_sdk`: Full description of the \`klyo-gry-sdk.js\` kit: how a game embedded in the catalogue sends a score to the leaderboard, saves progress on the server, asks for full screen, inserts an ad break, offers a REWARDED ad and lets the player record a clip. Read-only, needs no input. CALL THIS RIGHT AFTER klyo
- `klyo\_game\_cover`: Set the tile players recognise the game by in the catalogue. Frames are screenshots FROM YOUR RUNNING GAME: we take them ourselves once the game is live at its own address, so they appear only AFTER release \(\`klyo\_publish\_game\`\), not during it. Call without \`klatka\` to get the list of available fram
- `klyo\_fix\_game`: Change the CONTENT of a game that is already in the catalogue: name, tagline, description, how to play on a phone and on a computer, round length, genre, shelves, mood, game languages, screen layout, score limit, stage, store links, content questionnaire and age. It does NOT touch the package: repla
- `klyo\_game\_diagnostics`: WAITING PACKAGE VERSIONS: with a new upload\_id pass poprzednia\_paczka \(the currently selected upload\_id\) to append a version of the same draft. With an older upload\_id pass przywroc: true to select it again. Ownership, conflicts and retention are checked by the server. The 3 most recently selected v
- `klyo\_game\_files`: Your game's files to read, without a ZIP from the owner. Target: a game's \`slug\` or a waiting-room package's \`upload\_id\`. Without \`path\` you get the list \(path, size, whether it is text, \`hash\`\); with \`path\`, the content of one text file, up to 200 KB at a time \(read further with \`from\_line\`, narrow
- `klyo\_game\_patch`: Edits a game's text files \(html, htm, js, mjs, css, json, svg, txt, xml, webmanifest\) without a ZIP. Target: a game's \`slug\` or a waiting-room package's \`upload\_id\`. The first edit opens a WORKSHOP: a copy of the game next to the version players have, with its own preview address. Players keep playi
- `klyo\_game\_play`: Really play your game and see it: you send input steps, you get screenshots \(image content\) and the game state. It runs on the OWNER'S device, never on the klyo server: the owner opens the klyo studio \(https://dev.klyo.pl/\) on a computer or phone and clicks "Allow" under "Your assistant wants to pla
- `klyo\_game\_translate`: Translations of a game's texts into the klyo languages \(pl, en, de, fr, es, pt, it, ru, uk, tr\). YOU TRANSLATE: the owner's assistant, on the owner's own AI plan; klyo runs no model and does not pay for translation. Two steps in one tool: \(1\) call with only \`slug\` to get the original field by field
- `klyo\_creator\_card`: The developer's profile card on games.klyo.pl: “about me” and the tagline under the name. YOU WRITE: the owner's assistant, on the owner's own AI plan; klyo runs no model. Without \`o\_mnie\` and \`haslo\` we return the current card, the released games \(the only material you may write from\) and the rules
- `klyo\_fill\_game\_form`: Types fields into the OPEN “New game” form in the developer's studio \(dev.klyo.pl\); the owner watches them fill in, corrects them and submits the form THEMSELVES. You write, on the owner's own AI plan; klyo runs no model and saves nothing: it is a draft in their browser. Without \`pola\` you get the l
- `klyo\_add\_post`: Write a post in the klyo games community: a question, a request for playtesters, a launch or a game showcase. The post is visible immediately, with no moderation queue, and can be linked to a game from the catalogue \(\`gra\_slug\`\); then readers get a “play” button. Examples: • Write a post on klyo abo
- `klyo\_status`: State of this connection to klyo: server version, key scope, account role, how many tools you see and whether you may write, plus the state of integrations \(Google Search Console, Google Ads, AdMob, and for the owner also Cloudflare\), each as \`ok\`, \`not\_connected\`, \`auth\_error\` or \`no\_data\`, with wh

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html