Publish a browser game from Cursor

Cursor can publish the game from its integrated terminal as soon as the browser build is ready. There is no Playfrog signup before the first publish.

Ask Cursor:

> Build the game, find the output folder containing index.html, and publish that folder to > Playfrog. Return the play link and claim link. Do not expose the manage credential.

Cursor can run:

npx playfrog ./game

If your framework outputs to dist, use npx playfrog ./dist. The CLI supports static games up to 50 MB.

Connect Playfrog to Cursor

You can also add Playfrog as an MCP server in .cursor/mcp.json:

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

The MCP tools can publish or update games from files available to Cursor. Inline MCP uploads are limited to 8 MB, so the terminal command remains the better choice for larger builds.

Claim, share, and update

Share the returned play URL. Open the private claim URL within seven days to make the game permanent. Do not share the manage token.

After editing the game, tell Cursor:

> Rebuild the project and update the same Playfrog game with the new files. Keep the current public > URL and describe the change in one sentence.

The CLI records the game ID and update credential in .playfrog.json. Re-running it in the same folder updates the existing listing.

If you are looking for where to publish a web game made in Cursor, Playfrog lets Cursor finish the job instead of handing you a separate deployment setup.

Publish with Playfrog or browse more coding-agent guides.