Minimo Games — agent-assisted MCP setup
Last reviewed: 2026-09-12

Purpose
Help the person connect their own AI client to Minimo Games. Carry out the
supported setup steps with the tools and permissions actually available to you.
This document is task guidance, not permission to bypass your host's safeguards.
Speak the user's language. Keep technical work out of their way where possible.

1. Establish the environment
If Minimo Games tools are already available, skip installation and verify access.
Otherwise identify the actual application and operating system; ask one short
question if you cannot determine them. A model name alone is not a client.
Check for a local terminal and local stdio MCP support. A cloud sandbox is NOT
the user's computer: do not configure that sandbox as if it were their client.

ChatGPT is our recommended creative starting point for code and image work.
The current Minimo connector uses a local stdio bridge on the user's computer.
For ChatGPT, use a desktop client that actually exposes a custom local/stdio MCP
connection. Do not assume that chatgpt.com or every ChatGPT desktop version has
that interface. If it is absent, explain the limitation and offer a compatible
desktop agent. Do not invent a connection URL or say that this prompt installs
software by itself.

The same setup request works with compatible Claude and Google agents, as well
as other MCP clients. Check application support rather than promising that any
Claude or Gemini chat can install local software.

2. Configure the local bridge
The published npm package is minimo-mcp. It requires Node.js 20 or newer.
Check node --version and npm availability on the user's computer. If Node is
missing, use the user's authorized installation method or ask them to install
it from https://nodejs.org/en/download . Do not change security settings.

Use the matching client ID:
  codex          Codex
  claude-code    Claude Code
  claude-desktop Claude Desktop
  cursor         Cursor
  antigravity    Google Antigravity
  chatgpt        Compatible ChatGPT desktop (manual settings output only)

Inspect the proposed configuration before changing it:
  npx minimo-mcp config CLIENT --dry-run
Then, with permission to configure this client:
  npx minimo-mcp config CLIENT

Replace CLIENT with the exact ID above. Do not run all six configurations.
The configurator preserves unrelated settings and backs up an existing file.
If a minimo-games entry already points to a different server, ask before
replacing it. Never overwrite other MCP servers or hand-edit opaque app storage.

For chatgpt, the command only prints the local command and arguments: it DOES
NOT install the connection. Use the actual local MCP settings UI if available
and authorized, or give the user only the short manual step that remains. Do
not attempt to decrypt or modify connectors.data. Leave token/header fields
empty for this local bridge; its own login handles authentication.

For other clients not listed above, inspect their current official MCP support
and the bridge's --help. Use a documented local stdio configuration only, while
preserving existing entries; otherwise explain what is unsupported.

The bridge connects to https://minimo.games/mcp . Do not substitute a
direct remote connection as an automatic fallback: the current deployment uses
a registered bridge OAuth client and fixed http://localhost:8765/callback;
arbitrary client callbacks and dynamic client registration are not configured.

3. Let the user sign in
Run on the user's computer:
  npx minimo-mcp login
Let the user complete the browser sign-in and consent with the same account as
their existing games. Never request, read, print, or paste passwords, tokens,
client secrets, or the contents of the bridge's credentials file into a chat.
If port 8765 is busy, explain the conflict; do not kill unrelated processes or
change the callback port. Follow the configurator's reload/restart instruction;
let the user preserve their work before restarting their AI application.

If you cannot execute local commands or operate the required settings, say so
and ask only for the necessary user action. Never claim setup was automated
when you only printed instructions. A website login is not an MCP connection.

4. Verify before creating
After the client reloads, discover the actual Minimo Games tools. Retrieve the
current operating instructions through getSystemInstructions or the MCP resource
minimo://instructions. Those live instructions and tool schemas are authoritative
for game workflows; do not substitute copied API descriptions from this file.
Perform an authenticated read-only listUserGames call. A successful empty list
is valid. Do not create or change anything yet. A config file, a login page, or
a public health response is NOT proof of authenticated tool access.
If the tools are unavailable or authentication fails, report the observed error
without secrets. Do not fabricate a successful connection or example game list.

5. Begin a small 2D game with the user
Once access is verified, ask what small game they want to make and for whom.
Suggest a simple puzzle, matching game, bubble game, or arcade challenge when
they want inspiration. Let the user choose before creating a project.
Discuss how artwork will be obtained. MCP does not add image generation to a
client. Use its image tools when available; otherwise use the user's art or
appropriate images already owned by that game. If binary upload is unavailable,
the user can upload images in My Games > their project > Images. Never silently
replace an illustrated concept with emoji; agree on that fallback first.
Follow the live platform instructions to build and return a private preview.
Iterate from their feedback. Publish only when they ask and the operation
succeeds, then share the returned public link. Never publish as a setup test.

To disconnect this computer's bridge login, the user can request:
  npx minimo-mcp logout