@maka/maka-cli 5.143.0 → 5.143.1

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.143.0",
+  "version": "5.143.1",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",

package/bundle/typescript/src/commands/game/sideQuest-backlog-mcp.sub.cmd.js

@@ -1,10 +1,17 @@
+import fs from 'fs';
 import path from 'path';
 import { Command } from '../../command.js';
+import { UsageError } from '../../error.js';
 export function registerBacklogMcp(parent) {
     return Command.create({
         name: 'mcp',
-        usage: 'maka play:backlog:mcp [--env <env>]',
-        mustBeInMakaProject: true,
+        usage: 'maka play:backlog:mcp [--env <env>] [--site <path>]',
+        // OFF, DELIBERATELY -- see the file header. The framework's own
+        // check fires before this handler runs at all and only knows how
+        // to look at process.cwd(); --site is this command's own way to
+        // satisfy the same requirement, so it needs the chance to try that
+        // first rather than being refused upstream of ever seeing it.
+        mustBeInMakaProject: false,
         // NO maxArgLength HERE, DELIBERATELY. Command's own arg-length check
         // is `args.length >= maxArgLength` (command.ts), so `maxArgLength: 0`
         // refuses EVERY invocation regardless of what was typed -- an
@@ -17,29 +24,43 @@ export function registerBacklogMcp(parent) {
                 name: 'env',
                 description: 'Which maka-cli.com config/<env>/process.env supplies the Auth0 M2M credentials (default: production).',
             },
+            {
+                name: 'site',
+                description: 'Path to a maka-cli.com checkout. Defaults to resolving one from the current working directory if omitted -- pass this explicitly when the launching MCP client does not set cwd reliably.',
+            },
         ],
         shortDesc: 'Run an MCP server exposing game-backlog admin tools, authenticated as the M2M service account.',
         description: `Starts a local MCP server (stdio transport) with tools for listing and reading
     backlog items, attaching evidence and advancing status, drafting an AI bench, and posting
     admin notes -- all against maka-cli.com's existing game-backlog REST API, authenticated as
     the claude-agent@maka-cli.com service account via the Auth0 M2M token exchange
-    (api/v1/auth/m2m-login). Must be run with its working directory set to a maka-cli.com
-    checkout, since that project's config/<env>/process.env is where AUTHZERO_DOMAIN /
-    AUTHZERO_CLIENT_ID / AUTHZERO_SECRET / AUTHZERO_AUDIENCE live.`,
+    (api/v1/auth/m2m-login). Needs a maka-cli.com checkout to read AUTHZERO_DOMAIN /
+    AUTHZERO_CLIENT_ID / AUTHZERO_SECRET / AUTHZERO_AUDIENCE from config/<env>/process.env --
+    pass --site explicitly, or run with cwd already set to one.`,
         examples: [
-            'maka play:backlog:mcp',
-            'maka play:backlog:mcp --env local',
+            'maka play:backlog:mcp --site C:\\path\\to\\maka-cli.com',
+            'maka play:backlog:mcp --env local --site C:\\path\\to\\maka-cli.com',
         ],
     }, async function (_args, opts) {
         const env = opts.env ?? 'production';
-        if (!this.cfg.checkConfigExists(env)) {
-            // Pre-handshake failure -- nothing has touched stdout as MCP
-            // protocol yet, so a plain thrown Error (which Command's own
-            // wrapper reports via Log.error) is fine here.
-            throw new Error(`No configuration: ${env}, consider running "maka g:config ${env}"`);
+        let processEnvPath;
+        if (opts.site) {
+            const siteConfigDir = path.join(path.resolve(opts.site), 'config', env);
+            processEnvPath = path.join(siteConfigDir, 'process.env');
+            if (!fs.existsSync(processEnvPath)) {
+                throw new UsageError(`No config/${env}/process.env under --site ${opts.site} (looked for ${processEnvPath}).`);
+            }
+        }
+        else {
+            if (!this.cfg.checkConfigExists(env)) {
+                // Pre-handshake failure -- nothing has touched stdout as MCP
+                // protocol yet, so a plain thrown Error (which Command's own
+                // wrapper reports via Log.error) is fine here.
+                throw new UsageError(`Not in a maka-cli.com checkout and no --site given (looked for config/${env} under ${process.cwd()}).`);
+            }
+            const configPath = this.cfg.getAppConfigPath(env);
+            processEnvPath = path.join(configPath, 'process.env');
         }
-        const configPath = this.cfg.getAppConfigPath(env);
-        const processEnvPath = path.join(configPath, 'process.env');
         const [domain, clientId, clientSecret, audience] = await Promise.all([
             this.dotenvx.get('AUTHZERO_DOMAIN', processEnvPath),
             this.dotenvx.get('AUTHZERO_CLIENT_ID', processEnvPath),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.143.0",
+  "version": "5.143.1",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",