iDos Games MCP

Official Model Context Protocol servers for iDos Games, a backend and publishing platform for web games. 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:

	iDos Games (com.idosgames/platform)	iDos Games SDK (com.idosgames/sdk)
What it works on	Your live games: their data	Game code in your project
Where it runs	Hosted: https://site.idosgames.com/api/v2/mcp	Locally: npx -y @idosgames/mcp
Transport	Streamable HTTP	stdio
Sign-in	OAuth 2.1, you pick the games and permissions	None (public, read-only)
Works in browser-only clients (claude.ai, ChatGPT)	Yes	No, it needs a client that can start a local process

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:

• Find your games by name and see what it is allowed to do in each (list_my_titles).
• 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.
• 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.

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

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

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:

Tool	Purpose
list_modules	Catalog of composable game modules (games and systems: store, quests, inventory, leaderboard…)
get_module	One module's full source and install instructions
get_host_scaffold	The base every new project starts from (sign-in, lobby, config)
get_manifest	Runtime @idosgames/* packages and their exact versions
list_skills / get_skill	How to code against @idosgames/core, the module contract and composition
search	Find a ready module by the feature you need

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.

claude mcp add idosgames-sdk -- npx -y @idosgames/mcp

npm: @idosgames/mcp.

Both servers in one config

Cursor, .cursor/mcp.json:

{
  "mcpServers": {
    "idosgames": { "url": "https://site.idosgames.com/api/v2/mcp" },
    "idosgames-sdk": { "command": "npx", "args": ["-y", "@idosgames/mcp"] }
  }
}

VS Code, .vscode/mcp.json:

{
  "servers": {
    "idosgames": { "type": "http", "url": "https://site.idosgames.com/api/v2/mcp" },
    "idosgames-sdk": { "type": "stdio", "command": "npx", "args": ["-y", "@idosgames/mcp"] }
  }
}

Windsurf, ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "idosgames": { "serverUrl": "https://site.idosgames.com/api/v2/mcp" },
    "idosgames-sdk": { "command": "npx", "args": ["-y", "@idosgames/mcp"] }
  }
}

Claude Code, .mcp.json:

{
  "mcpServers": {
    "idosgames": { "type": "http", "url": "https://site.idosgames.com/api/v2/mcp" },
    "idosgames-sdk": { "command": "npx", "args": ["-y", "@idosgames/mcp"] }
  }
}

Example prompts

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

• Documentation: idosgames.com/mcp
• Support: idosgames.com/mcp#support, [email protected]
• Privacy policy: idosgames.com/privacy
• Terms: idosgames.com/terms

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.