@cueportal/make-a-game

An MCP server that lets AI coding assistants (Claude Code, Codex, and any other MCP client) build, test and publish games on CUE Portal. It exposes everything the in-browser Studio can do as tools: create a game, edit its details, upload source and assets, publish and unpublish, plus the live developer documentation.

Set up

# Claude Code
claude mcp add cue npx @cueportal/make-a-game

# Codex
codex mcp add cue -- npx @cueportal/make-a-game

# then sign in (once)
npx -y @cueportal/make-a-game login

You also need a CUE Portal account with the developer terms accepted (in the browser: Profile → Make a Game). The full guide lives on the portal at /developers/setup.html.

What it can do

create_game, list_my_games, list_my_teams, get_game, update_game, set_thumbnail, set_feature_graphic, list_files, read_file, write_file, upload_asset, download_asset, push_directory, delete_file, submit_game, withdraw_game, unpublish_game, get_test_url, get_debug_log, get_documentation, get_cards, get_card, list_shop_items, create_shop_item, update_shop_item, set_shop_item_image, delete_shop_item.

Test runs record the game's console output and errors, and get_debug_log reads the latest run back, so the assistant can debug from what actually happened instead of a description of the screen.

Games are plain JavaScript with no build step. The only allowed imports are the game's own files by relative path plus four pinned libraries the platform serves: @cue/sdk (cards, player, economy, save state, multiplayer, and the <cue-card> element), @cue/2d (a canvas engine for card games with real animation, particles and effects), @cue/3d (a 3D world with a character and camera) and @cue/rules (the real CUE card abilities, up to a full server-run match). The platform enforces the import rule on every upload, and the portal, not the game, stays the sole authority over player identity, collections and currency.

get_documentation serves the live docs for all of it, and the assistant is told to read them before writing code: sdk-api, add-a-game, 2d, 3d, rules, setup.

Configuration

• CUE_TOKEN - use this session token instead of the stored one.
• CUE_PLATFORM_URL / CUE_PORTAL_URL - point at a different deployment (defaults are the production CUE Portal).

Tokens are stored in ~/.config/cueportal/credentials.json, keyed by platform URL. Your password is never stored.