@idosgames/mcp 0.1.18 → 0.1.19

package/dist/cli.js

@@ -48,7 +48,7 @@ function moduleExportName(id) {
 var TOOLS = [
   {
     name: "list_modules",
-    description: "List the composable iDosGames modules in the catalog. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a capability to add on top), engine, genre, a short summary, what it 'provides' (its features), tags, preview media, a live demo url, and its dependency count. Read 'provides' to reuse a ready module instead of building the feature from scratch, then get_module to pull its source. Entries may also carry 'sharedUi' ({provides, requires, drawsOwn}: shared chrome roles currency-bar | wallet | status | account \u2014 a provider such as game-hud draws them once for every mode, and templates hide their own copies automatically; mixing two or more templates \u2192 install game-hud) and 'events' ({emits: [{topic, when, payload}], listens: [{topic, why}]}). To react to another module's event, copy its payload descriptor into your own defineTopic(topic, shape(payload)) \u2014 never import another module.",
+    description: "List the composable iDosGames modules in the catalog. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a capability to add on top), engine, genre, a short summary, what it 'provides' (its features), tags, preview media, a live demo url, and its dependency count. Read 'provides' to reuse a ready module instead of building the feature from scratch, then get_module to pull its source. Entries may also carry 'sharedUi' ({provides, requires, drawsOwn}: shared chrome roles currency-bar | wallet | status | account | menu | modes \u2014 the project's base (sign-in + the lobby, see get_host_scaffold) provides currency-bar, wallet, account, menu and modes, and a game hides its own copies automatically) and 'inBase' (true: a system installed with the base in every new project \u2014 the shop, heroes, leaderboards\u2026; its screen is a tab of the lobby) and 'events' ({emits: [{topic, when, payload}], listens: [{topic, why}]}). To react to another module's event, copy its payload descriptor into your own defineTopic(topic, shape(payload)) \u2014 never import another module.",
     inputSchema: { type: "object", properties: {} }
   },
   {
@@ -83,7 +83,7 @@ var TOOLS = [
   },
   {
     name: "get_host_scaffold",
-    description: "Get the host-shell scaffold (index.html, main.tsx, empty src/modules.ts, config) for a NEW project. Write these to the project root, then add modules with get_module.",
+    description: "Get the base every NEW project starts from \u2014 the host shell with sign-in and the lobby (index.html, main.tsx, src/base/, src/app.config.ts, empty src/modules.ts, config). Write these to the project root, then add modules with get_module: the systems with inBase (shop, heroes, leaderboards\u2026) and the game(s).",
     inputSchema: { type: "object", properties: {} }
   },
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idosgames/mcp",
-  "version": "0.1.18",
+  "version": "0.1.19",
   "description": "MCP server that serves the iDosGames Module & Skills Registry to AI coding agents (Claude Code, Codex, Cursor…): list/pull composable game modules and the host scaffold, and load skills for @idosgames/core, the module contract, and composition.",
   "type": "module",
   "license": "MIT",