[iDos Games]
iDos Games MCP
Official Model Context Protocol servers for
iDos Games, a backend and publishing platform for cross-platform games (web, Android, iOS, PC) with web3 support. Connect them to Claude,
ChatGPT, Cursor, VS Code, Codex or any other MCP client, and your AI assistant can build, configure and ship
your games.
There are two servers, and they do different jobs:
Both serve the same catalog of game modules, the project scaffold and SDK skills, so a browser-only client
(claude.ai, ChatGPT) gets them from the hosted server. A game's live config, generated assets, task board and
builds go only through the iDos Games server; the SDK server needs no sign-in and works offline.
iDos Games (hosted)
What your assistant can do with it:
- Find your games by name and see what it is allowed to do in each (
list_my_titles).
- Create a new game (
create_title, its own permission): the same way the dashboard does, it takes a slot of
your plan and gets the base systems, a game module, a ready starter build and a sandbox (DEV) copy. The new game
joins the assistant's access at once, so it can configure and ship it next.
- Read and update game configuration section by section: virtual currencies, items, store, lootboxes,
quests, timed and co-op events, seasons, leaderboards, crafting, rewards, premium, tutorials, A/B
experiments, localization, chat, multiplayer, push, advertising and more (
get_<section> / save_<section>).
Each section is saved on its own, so the rest of the configuration stays untouched.
- Web3: game currencies as on-chain tokens and items as NFTs on EVM networks and Solana, player deposits
and withdrawals through the reward pool, token-gated play and wallet login, networks, contract addresses and
gas policy (
get_blockchain / save_blockchain, crypto currencies in save_currency, NFT items in
save_item). Token launch and holder staking live on idosgames.com itself.
- Title data and localization keys: the game's shared key-value data and its text keys.
- Server logic: publish CloudCode, and list secret names (values are never returned).
- Generate assets with AI: images, speech and sound, music, short videos, 3D models and text. Generation
spends your account's credits, so the assistant can check
list_ai_tiers and estimate_media_cost before
running it.
- Task board: projects, columns, cards, assignees and comments.
- Ship builds: upload a ready web build, get a test link, then put it live for players.
- Game modules and SDK skills (read-only, no game needed): the project scaffold (
get_host_scaffold), ready
games and systems such as store, quests, inventory, leaderboard and multiplayer (list_modules,
search_modules, get_module), exact SDK package versions (get_manifest) and how-to skills for the SDK
(list_skills, get_skill).
- Video studio catalog (read-only, no game needed): the formats of short videos and everything a video can
name (
list_video_formats, get_video_format), the library of ready characters, scenes and music
(search_assets) and complete example videos (list_video_templates).
- Write videos for the video studio (paid with credits):
plan_video turns an idea into a ready video by the
studio's AI director, generate_asset makes a character, scene, prop or music for it and puts it in its place.
The answer is the video package ({ spec, assets }) and a link that opens it in the app's editor; the MP4 is
made on the player's device. publish_asset puts the assets into the app's Workshop as its official content.
Every tool has a title and readOnlyHint / destructiveHint / openWorldHint annotations; create_title
also says idempotentHint: false (every successful call is another game).
How sign-in works
Add the server as a plain HTTP MCP server with no headers and no API key. initialize and tools/list
need no sign-in. The first tool call answers 401, your client opens the iDos Games sign-in page, and you pick
which games the assistant may use and what it may do in each (read config, write config, generate assets,
upload builds…), and whether it may create new games. The client then repeats the call. You can revoke access at any time in Connected apps on
platform.idosgames.com.
Connect
Claude (claude.ai, Desktop, mobile): Settings → Connectors → Add custom connector →
https://site.idosgames.com/api/v2/mcp.
Claude Code
ChatGPT: Settings → Apps & Connectors → Advanced → Developer mode → Create, URL
https://site.idosgames.com/api/v2/mcp, authentication OAuth.
Codex CLI
Gemini CLI
Cursor (.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json, key serverUrl),
VS Code (.vscode/mcp.json): see Both servers in one config.
iDos Games SDK (local)
Serves the iDos Games Module & Skills Registry to coding agents:
All tools are read-only and return content. The agent writes the files into its own project. The registry is
bundled in the package, so it also works offline.
npm: @idosgames/mcp.
Both servers in one config
Cursor, .cursor/mcp.json:
VS Code, .vscode/mcp.json:
Windsurf, ~/.codeium/windsurf/mcp_config.json:
Claude Code, .mcp.json:
Example prompts
- "Create a new idle RPG called Moon Farm and give it three currencies."
- "Show the virtual currencies and store items configured for my game."
- "Add a daily quest that rewards 100 gold for winning 3 matches."
- "Generate a 512×512 icon for a fire sword and add it to the item catalog."
- "Start a new idle RPG project with a store and daily quests." (SDK server)
- "Build the game and upload it as a test version." (both servers)
- "What tasks are assigned to me on my board?"
Links
License
The SDK server (@idosgames/mcp) is MIT-licensed; see LICENSE. The hosted iDos Games server is a
service covered by the iDos Games terms.
