@ductape/mcp 0.2.2 → 0.2.3

package/dist/index.js

@@ -11,6 +11,8 @@
  */
 import { createRequire } from 'module';
 import { execSync } from 'child_process';
+import { homedir } from 'os';
+import { delimiter, join } from 'path';
 import { z } from 'zod';
 import { executeViaProxy, generateExecutablePayload, getAssetSchemas, } from './proxy-client.js';
 const MODULES = [
@@ -141,9 +143,10 @@ There are THREE categories of operations. Use the right tool for each:
            ductape_cli("resources database create -f db-config.json")
        This applies to: products, apps, and resources (databases, storage, caches, etc.),
        cloud connections, and secrets. Environments have their own CLI commands (see below);
-       app actions, auths, quotas, fallbacks, jobs, and healthchecks are configured in the
-       Workbench UI. Features have no CLI create command because their definitions are code-first
-       through features.define.
+       App actions and auths are configured in the Workbench UI. Quotas, fallbacks, jobs, and
+       healthchecks are administrative resources managed with ductape_cli("resources <type> ...").
+       Features have no CLI create command because their definitions are code-first through
+       features.define.
 
        ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
        messageBroker, graph, vector, and any other resource with an envs array):
@@ -1175,15 +1178,19 @@ function checkCli() {
     try {
         const out = execSync('ductape --version', {
             encoding: 'utf8',
-            timeout: 5000,
+            timeout: 15000,
             stdio: ['pipe', 'pipe', 'pipe'],
             env: cliEnvironment(),
             cwd: cliCwd(),
         }).trim();
         return { available: true, version: out || 'unknown' };
     }
-    catch {
-        return { available: false };
+    catch (error) {
+        const message = String(error?.stderr || error?.message || error);
+        const commandMissing = error?.code === 'ENOENT' ||
+            error?.status === 127 ||
+            /\b(command not found|not recognized as an internal|no such file or directory)\b/i.test(message);
+        return { available: !commandMissing };
     }
 }
 function checkLoginState() {
@@ -1298,6 +1305,18 @@ function runCli(command) {
 function cliEnvironment() {
     const environment = { ...process.env };
     delete environment.DUCTAPE_ACCESS_KEY;
+    const pathKey = Object.keys(environment).find((key) => key.toLowerCase() === 'path') ?? 'PATH';
+    const configuredPath = environment[pathKey] ?? '';
+    const fallbackBins = [
+        join(homedir(), '.npm-global', 'bin'),
+        join(homedir(), '.local', 'bin'),
+        '/opt/homebrew/bin',
+        '/usr/local/bin',
+    ];
+    environment[pathKey] = [...new Set([
+            ...configuredPath.split(delimiter).filter(Boolean),
+            ...fallbackBins,
+        ])].join(delimiter);
     return environment;
 }
 /**
@@ -2788,10 +2807,13 @@ Resilience covers three mechanisms: quotas (rate-limited provider pools), fallba
 provider switching), and healthchecks (continuous probe monitoring with failure actions).
 
 CONFIGURATION BOUNDARY
-  Quotas, fallbacks, and health checks are administrative product configuration. Configure them in
-  Workbench (or a future access-key administrative tool explicitly documented for the asset).
-  Never route administrative create/update methods through ductape_execute: its publishable-key
-  runtime proxy will fail.
+  Quotas, fallbacks, and health checks are administrative product configuration. Manage them with
+  the authenticated CLI:
+    ductape_cli("resources quota ...")
+    ductape_cli("resources fallback ...")
+    ductape_cli("resources health ...")
+  Workbench is also supported. Never route their administrative create/update methods through
+  ductape_execute: its publishable-key runtime proxy will fail.
 
 QUOTAS — rate-limited multi-provider pools:
   Workbench definition shape:
@@ -4332,8 +4354,9 @@ const cliInputSchema = z.object({
         'resources (databases, storage, caches…), event broker topics, cloud connections, secrets, ' +
         'and for apply/migrate workflows.\n\n' +
         'Note: environments have their own CLI commands (products environments list/get/create/update, ' +
-        'no linked project required — the product tag is always an explicit argument). App actions, ' +
-        'quotas, fallbacks, and jobs are configured in the Workbench UI. Features also have no CLI ' +
+        'no linked project required — the product tag is always an explicit argument). Quotas, ' +
+        'fallbacks, jobs, and healthchecks use resources commands. App actions and auths are ' +
+        'configured in the Workbench UI. Features have no CLI ' +
         'creation command: define them in application code with features.define so application ' +
         'boot/runtime registration makes them available.\n\n' +
         'The CLI uses the user\'s local logged-in session (ductape login) — no key is required.'),
@@ -4788,13 +4811,14 @@ async function main() {
                 '    After importing, create topics first with ductape_cli("events topics create -f topic.json") — SQS requires explicit topic creation with queueUrls. For other providers, topics auto-register on first produce but should still be created explicitly before any consumer subscribes.\n' +
                 '  - Listing workspaces, products, focused product components, secrets\n' +
                 '    Prefer "products components list --product-tag <tag> --json" for compact inventory; use\n' +
-                '    "products components get --product-tag <tag> --type notifications|events --json" for focused detail.\n' +
+                '    "products components get --product-tag <tag> --type notifications|events|healthchecks|features --json" for focused detail.\n' +
                 '  - Managing notification components and message templates through "resources notifications" and "notifications messages"\n' +
                 '  - Linking a project folder: "link --product <tag> --env <slug>"\n' +
                 '  - Syncing sessions/notifications/events: "apply" or "apply sessions" etc.\n' +
                 '  - Running database migrations: "db migrate", "db schema generate"\n\n' +
-                'NOTE: Environments have their own CLI commands (products environments *). App actions, ' +
-                'auths, quotas, fallbacks, and jobs are configured in the Workbench UI. Features have no ' +
+                'NOTE: Environments have their own CLI commands (products environments *). App actions ' +
+                'and auths are configured in the Workbench UI. Quotas, fallbacks, jobs, and healthchecks ' +
+                'are managed with resources commands. Features have no ' +
                 'CLI creation command because definitions are code-first through features.define and ' +
                 'registered by the application runtime.\n\n' +
                 'DO NOT use ductape_execute for admin operations — it uses a publishable key which only ' +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",