iDos Games SDK MCP server

<!-- mcp-name: com.idosgames/platform --> <!-- mcp-name: com.idosgames/sdk -->

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:

Rule of thumb: game code goes through the SDK server. A game's live config, generated assets, task board and builds go through the iDos Games server.

iDos Games (hosted)

What your assistant can do with it:

quests, timed and co-op events, seasons, leaderboards, crafting, rewards, premium, tutorials, A/B experiments, localization, chat, multiplayer, push, advertising and more (get / save). Each section is saved on its own, so the rest of the configuration stays untouched.

• Find your games by name and see what it is allowed to do in each (listmytitles).
• Read and update game configuration section by section: virtual currencies, items, store, lootboxes,

and withdrawals through the reward pool, token-gated play and wallet login, networks, contract addresses and gas policy (getblockchain / saveblockchain, crypto currencies in savecurrency, NFT items in saveitem). Token launch and holder staking live on idosgames.com itself.

• Web3: game currencies as on-chain tokens and items as NFTs on EVM networks and Solana, player deposits

spends your account's credits, so the assistant can check listaitiers and estimatemediacost before running it.

• 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

• 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.

Every tool has a title and readOnlyHint / destructiveHint / openWorldHint annotations.

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…). 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

claude mcp add --transport http idosgames https://site.idosgames.com/api/v2/mcp

ChatGPT: Settings → Apps & Connectors → Advanced → Developer mode → Create, URL https://site.idosgames.com/api/v2/mcp, authentication OAuth.

Codex CLI

codex mcp add idosgames --url https://site.idosgames.com/api/v2/mcp

Gemini CLI

Shortened. The full README is on GitHub.