All servers · Marketing & SEO · Build & deploy · APIs & integrations

klyo games: publish HTML5 browser games

pl.klyo/games · v1.2.0

Measured by MCP Station

Instruction-like text was found in klyo_game_translate, klyo_publish_game. This is a pattern match, not a verdict. What we look for

Description written by the publisher, not verified

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

Connect

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

Tools as reported by the server

• 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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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

Tool changes

• 2026-10-24: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_analytics, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk
• 2026-10-22: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_analytics, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk
• 2026-10-21: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_analytics, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk
• 2026-10-20: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk, klyo_game_cover
• 2026-10-17: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk, klyo_game_cover
• 2026-10-16: klyo_my_games, klyo_publish_game, klyo_upload_package, klyo_update_game, klyo_release_rollback, klyo_release_version, klyo_delete_game, klyo_game_stats, klyo_game_requirements, klyo_game_scaffold, klyo_game_sdk, klyo_game_cover

Repository · Website · JSON · Text for agents · Registry updated 2026-09-30