Give your AI a way to share your game.

Start Docker. In the PlayPrompt project folder, run the setup commands below. Keep Docker running. Your game folder should contain index.html and the files the game needs.

docker compose up --build -d
docker compose --profile tools build mcp

Include only the game: HTML, CSS, JavaScript, images, or WASM. Put index.html at the top of a folder or ZIP. Limits: 100 MiB ZIP, 500 MiB unpacked, 5,000 files. Server code, external API calls, Web Workers, and Service Workers are not supported.

Open the local PlayPrompt at localhost:3000. Sign in with your local test account, open its creator console, and make an API key there. This key must belong to the local server running in Docker. Save it in your private local settings; never send it in an AI message.

With the local development setup, sign-in messages go to the test mailbox. Open the message link, then finish signing in. This is a development mailbox, not your personal inbox.

Create playprompt-mcp.env outside your game folder and save the key and game-folder path there. Add the Docker stdio example below to Cursor’s ~/.cursor/mcp.json. Replace every example path with your own full path. Keep any existing servers.

In mcpServers, add only the playprompt entry if other servers already exist. envFile belongs to Cursor; --env-file tells Docker Compose which settings file to read. Point both to the same private file and keep it out of Git.

PLAYPROMPT_API_KEY=YOUR_PRIVATE_KEY_FROM_THE_CONSOLE
PLAYPROMPT_GAME_DIR=/ABSOLUTE/PATH/TO/YOUR/GAME

{
  "mcpServers": {
    "playprompt": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "compose",
        "--project-directory",
        "/ABSOLUTE/PATH/TO/promptopia.games",
        "--env-file",
        "/ABSOLUTE/PATH/TO/playprompt-mcp.env",
        "run",
        "--rm",
        "-T",
        "--no-deps",
        "-e",
        "PLAYPROMPT_API_KEY",
        "mcp"
      ],
      "envFile": "/ABSOLUTE/PATH/TO/playprompt-mcp.env"
    }
  }
}

PLAYPROMPT_GAME_DIR is the full path to the folder you choose on your computer. Docker mounts only that folder, read-only, at /games. For a file inside it, use /games/game.html or /games/build.zip.

Reload MCP in your AI app. Look for deploy_game, get_deployment, list_games, and search_game_tips. Ask it to list your games first. With Docker, the selected game folder is called /games inside the container.

• deploy_game
• get_deployment
• list_games
• search_game_tips

Use the example request below. PlayPrompt checks the files and publishes the game if they pass. Open the returned play link. If the status is processing, ask for the deployment status instead of uploading again.

Say this to your connected local AI app

Publish the game in /games to PlayPrompt. Call it Space Runner. Give me the play link when it is ready.

{
  "local_path": "/games",
  "title": "Space Runner"
}

{
  "local_path": "/games",
  "game_id": "YOUR_GAME_ID"
}