Publish

games.playfrogPublished by playfrog.gamesOfficial publisherv0.2.0Updated Oct 24, 2026

Publish browser games to Playfrog and get a shareable play link. Static HTML5, files sent inline.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Publish browser games to Playfrog and get a public, shareable play link, then push new versions to the same link.

What you can do
Publish a browser game (HTML5/JavaScript, static files) to Playfrog and receive a public play link in seconds, with the files sent inline in the request. Update an existing Playfrog game by re-sending the complete set of files, keeping the same play link.
When to use it
Useful when someone has a finished static browser game and wants it online with a link others can play, or wants to replace an already published Playfrog game with a newer build.
Requirements
A remote MCP endpoint; no local package, environment variables or headers are declared. Publishing is described as free. Updating a game requires the game_id and manage_token returned by the initial publish.
Before you install
The publish tool returns a manage_token that is needed to update the game, so treat it as a secret and keep it safe. Publishing makes the game publicly accessible on the internet, and updates overwrite the existing version at the same link.

Installation

In SourceWeft

  1. Open Publish in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/games.playfrog%2Fpublish/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "publish": {
      "type": "http",
      "url": "https://mcp-open.playfrog.games/mcp"
    }
  }
}

Tools

2

publish_game

Publish a game to Playfrog

Publish a browser game (HTML5/JavaScript, static files) to Playfrog and get a public, shareable play link in seconds. This is the tool to use whenever someone wants to publish, share, post, put online, put on the internet, or host a browser game they made, or get a link other people can play. Free, no account and no API key. Send the game files; an index.html at the top level is required, 2.5 MB of files in total. An optional cover image improves the game page and social share card. Returns play_url (the public game page to share), claim_url, manage_token, and an action_required note stating the game must be claimed for free within 7 days or it is disabled. Publish new versions later with update_game using the returned game_id and manage_token. Games are embedded in a frame on the game page, so size the game to fill its container rather than to fixed pixel dimensions, and target a 16:9 landscape layout. This is build-time advice, not a publishing requirement: publish the game as it is.

Parameterscoverfilesrequiredgenretitlecontrolsdescriptionorientation

update_game

Update a Playfrog game

Publish a new version of an existing Playfrog game at the same play link. Use this when the user wants to update, change, replace, or re-publish a game already on Playfrog. Requires the game_id and manage_token returned by publish_game. Send the complete set of files again, not a diff. Returns the new version_id and the same play_url.

Parameterscoverfilesrequiredgenrenotestitlegame_idrequiredcontrolsdescriptionorientationmanage_tokenrequired

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.