Publish a browser game from Windsurf

Windsurf can take a completed static game from the editor to a public Playfrog page. Publishing is free and the first upload does not need a Playfrog account.

Use this instruction:

> Check the production build for a top-level index.html. Publish the correct game folder to > Playfrog and show me the public play link and private claim link.

From the Windsurf terminal, the agent can run:

npx playfrog ./game

Publish the generated output folder, such as dist, when the source directory is not directly playable.

Add the Playfrog MCP server

Windsurf can use an MCP configuration at ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "playfrog": {
      "url": "https://mcp.playfrog.games/mcp"
    }
  }
}

The Playfrog tools support publishing and updating. MCP sends files inline and is limited to 8 MB. Use the CLI for games up to 50 MB.

Keep control of the game

Open the returned claim URL within seven days. Until it is claimed, the game is temporary. Claiming is free and keeps it available permanently. Share the play URL, not the claim URL or manage credential.

To ship a later version, ask Windsurf to rebuild and update the existing Playfrog game. Running the same command in the same folder reads .playfrog.json and keeps the public URL unchanged. Keep that credential file out of public repositories.

Playfrog answers the “where should I publish my web game?” question for Windsurf users with a workflow that stays inside the coding agent and ends with a page people can play.

Publish a game, see all guides, or read the full integration details.