Copy a task into your agent
No token neededPaste a task into the agent you already use. It reads the guide and starts changing your code — nothing to install.
See the tasksLoading page…
Develop with the AI tools you know. Shape the gameplay, test it on Mixel, and share a game worth coming back to.
Using your own agent and uploading a game does not consume Mixel AI credits.
Paste a task into the agent you already use. It reads the guide and starts changing your code — nothing to install.
See the tasksCreate a personal token and add the MCP endpoint to your client. Then your agent can read guides, upload previews and check release status itself.
Connect your agentGet a code for one project in the workshop. Send your changes back with the desktop Publisher, then play the version on the web and decide whether to keep it.
See project handoff stepsChoose the core action, a clear goal and one reason to replay. Build a small playable slice first.
Read Mixel’ development guide. Help me turn my idea into a small HTML game: define the player’s main action, feedback, a meaningful choice and a replay hook. Agree on a visual direction, build a playable slice, and test it before expanding. Keep my chosen engine and tools.
Keep what works. Identify the biggest issue in art, controls or pacing, then verify one change through play.
Read Mixel’ game-feel, art and playtest guidance. Inspect this game and identify the most important player-facing improvement. Preserve working behavior and assets. Make a focused change, play it, and report what was verified and what still needs human feedback.
Check the package, upload a private draft, test the preview and apply for a public release.
Read Mixel’ development and publishing guides. Check this project’s HTML entry, assets, controls and saves. Upload a private preview and check its status. Verify it in the platform player and report the preview URL and issues. Submit for public review only when I ask to publish.
Optional guidance for ideas, art, game feel and playtesting. Use the modules you need with your existing engine and tools.
HTML and ZIP games · optional SDK · isolated player · local saves first
Bundle required assets and use relative paths. Network access needs declared origins. Upload acceptance, a playable preview and a public release are different stages.
The downloadable kit and source guides are currently in English. Your agent can explain them in your language.
Loading…
Download the source, change one mechanic, then play it. Examples are starting points, not a required game style.
Upload, preview and release are three different stages — not one step.
Every stage shows its status in your games, and review results also arrive as notifications.
Open my gamesCreate a personal token in your account, then add the MCP endpoint in your client’s connection settings. Keep the token in the client’s secret settings, never in a prompt or game package.
Manage agent connectionshttps://mixel.games/mcpFirst install your AI client and complete its own model/account setup. Mixel uses a separate personal token and Streamable HTTP; OAuth sign-in is not available here.
Codex CLI, using its user configuration.
Based on official documentation. These six client applications have not yet been tested end to end with Mixel. Documentation checked：
Sign in to Mixel and create an Agent connection named after this client. Select games:read for the connection check. Uploading and submitting later also require builds:write and submissions:write. Copy the token when it is shown; it is displayed only once.
Create or manage a tokenOpen or create ~/.codex/config.toml in your home directory. Add the TOML block below.
If the file already exists, merge the mixel entry into it and keep your other servers and settings.
[mcp_servers.mixel]
url = "https://mixel.games/mcp"
bearer_token_env_var = "MIXEL_TOKEN"bearer_token_env_var adds the Bearer header. Do not use codex mcp login for this personal-token connection.
Run one of these commands in your local terminal, then enter the token at the hidden prompt. MIXEL_TOKEN contains only the token, without Bearer. Launch the client from that same terminal. Fully quit an already running app first; a desktop shortcut or a project .env file may not pass the variable to it. These commands apply to this terminal session only.
$env:MIXEL_TOKEN = Read-Host "Mixel personal token" -MaskInputread -r -s MIXEL_TOKEN
export MIXEL_TOKEN
printf '\n'Start Codex from the prepared terminal. Use /mcp in the session to inspect mixel, then run the identity-check task below.
codexSuccess means whoami returns your Mixel account and granted scopes, and the guide is readable. Seeing a server or a tool list alone does not verify authentication. You can also check Last used on the Agent connections page.
Only test the Mixel connection. Call the mixel server's whoami and get_development_guide tools. Report my account ID, granted scopes and guide version. Do not upload, modify or submit a game, and do not print any token.
The copied task includes Mixel' public address, docs and MCP endpoint so it works when sent on its own. Your agent still needs the client's network access and a personal token configured privately. Reading a guide does not install a Skill or supply local image generation/browser tools.
I want to make a playable HTML game for Mixel. Its official site is https://mixel.games. The agent-readable index is https://mixel.games/llms.txt; client setup is at https://mixel.games/developers#connect; the MCP endpoint is https://mixel.games/mcp. First check whether this session already has the mixel MCP server. If it does, call whoami, get_development_guide and get_publishing_guide and report my account and scopes. If it does not, use your available web tools to read the setup instructions and public guides at https://mixel.games/backend/api/v1/guides/development and https://mixel.games/backend/api/v1/guides/publishing. Explain how to configure this client. I will create my personal token at https://mixel.games/account/agents and enter it in the client's private settings; do not ask me to paste it into chat. If an address is unavailable or the service is not enabled, state that clearly instead of claiming a successful connection. Once the connection or documentation is confirmed, help me define one core mechanic and make a small playable HTML game. If available, consult the creation kit at https://mixel.games/backend/api/v1/creator-kit/download for design, art and playtesting guidance. Build and playtest locally first. Explain the private upload, owner preview and review submission steps; wait for my instruction before submitting for review.
Loading…