@ductape/mcp 0.2.1 → 0.2.2

package/dist/index.js

@@ -35,7 +35,24 @@ There are THREE categories of operations. Use the right tool for each:
            ductape_cli("cloud connections list")
            ductape_cli("link --product my-product --env dev")
        If the CLI is not installed, ductape_cli will return install instructions automatically.
-       NOTE: Environments and app actions are configured in the Workbench UI — there are no CLI commands for them.
+       NOTE: App actions are configured in the Workbench UI — there is no CLI command for them.
+       Environments DO have CLI commands: ductape_cli("products environments list/get/create/update ...").
+
+       RESOLVING "No linked project" ERRORS:
+       Some commands (declarative sync below, db migrate/schema, products environments *) need a
+       linked project — a local .ductape/config.json with a product tag and env slug. The "link"
+       command does NOT validate against the server: it just writes that local file. This means you
+       can run ductape_cli("link --product <tag> --env <slug>") even before that environment exists on
+       the product yet — do not treat "no linked environment exists server-side" as a reason to avoid
+       linking first. If the failing command already takes the product tag as an explicit argument
+       (e.g. products environments create/update/list/get), linking is not even required for it —
+       only commands that need to *infer* the product/env from local project state require a link.
+       Also: this MCP server runs the CLI subprocess in the directory named by the DUCTAPE_PROJECT_DIR
+       env var (falls back to this server process's own cwd if unset). If a command inexplicably
+       reports "no linked project" right after a successful "link" call, the project directory the
+       link was written to and the directory this server is running the CLI from may not match — set
+       DUCTAPE_PROJECT_DIR explicitly in this server's env (e.g. in the consuming project's .mcp.json)
+       to the target project's absolute path.
 
        DECLARATIVE SYNC  (apply sessions, notifications, events from code; run DB migrations)
        → Also use ductape_cli. The project must be linked first (ductape init --link).
@@ -123,9 +140,10 @@ There are THREE categories of operations. Use the right tool for each:
            ductape_cli("resources storage list")
            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, 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.
+       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.
 
        ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
        messageBroker, graph, vector, and any other resource with an envs array):
@@ -324,9 +342,9 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   IMPORTANT: ALL product.* methods require the access key and will return 403 with a publishable key.
   Use ductape_cli for ALL product operations — never ductape_execute:
     ductape_cli("products get --tag <tag> --json")           ← fetch product + full inventory
-    ductape_cli("products components list --tag <tag> --json") ← compact non-secret inventory
-    ductape_cli("products components get --tag <tag> --type notifications --json")
-    ductape_cli("products components get --tag <tag> --type events --json")
+    ductape_cli("products components list --product-tag <tag> --json") ← compact non-secret inventory
+    ductape_cli("products components get --product-tag <tag> --type notifications --json")
+    ductape_cli("products components get --product-tag <tag> --type events --json")
     ductape_cli("products create --name <name> --tag <tag>")
     ductape_cli("products environments list <tag> --json")
     ductape_cli("products environments get <tag> <slug> --json")
@@ -1160,6 +1178,7 @@ function checkCli() {
             timeout: 5000,
             stdio: ['pipe', 'pipe', 'pipe'],
             env: cliEnvironment(),
+            cwd: cliCwd(),
         }).trim();
         return { available: true, version: out || 'unknown' };
     }
@@ -1177,6 +1196,7 @@ function checkLoginState() {
             timeout: 10000,
             stdio: ['pipe', 'pipe', 'pipe'],
             env: cliEnvironment(),
+            cwd: cliCwd(),
         });
         authState = 'ok';
         return 'ok';
@@ -1197,6 +1217,7 @@ function syncWorkspace() {
             timeout: 10000,
             stdio: ['pipe', 'pipe', 'pipe'],
             env: cliEnvironment(),
+            cwd: cliCwd(),
         });
     }
     catch {
@@ -1225,6 +1246,7 @@ function runCli(command) {
             timeout: 90000,
             stdio: ['pipe', 'pipe', 'pipe'],
             env: cliEnvironment(),
+            cwd: cliCwd(),
         });
         return { success: true, output: output.trim() };
     }
@@ -1278,6 +1300,19 @@ function cliEnvironment() {
     delete environment.DUCTAPE_ACCESS_KEY;
     return environment;
 }
+/**
+ * Directory the `ductape` CLI subprocess runs in. Commands that resolve a linked project
+ * (findProjectConfig walking up from cwd — e.g. `products environments *`, `apply`, `db migrate`)
+ * depend on this being the user's actual project directory, not wherever this MCP server process
+ * itself happened to be spawned from. execSync inherits process.cwd() when no cwd is given, which
+ * is only correct if this server was started from inside the target project — that doesn't hold
+ * for every launch path (e.g. a host attaching this server to an already-running session whose
+ * cwd is unrelated to the project). Set DUCTAPE_PROJECT_DIR explicitly in the server's env
+ * (e.g. in .mcp.json) to pin it; falls back to this process's own cwd otherwise.
+ */
+function cliCwd() {
+    return process.env.DUCTAPE_PROJECT_DIR || process.cwd();
+}
 function shellArgument(value) {
     return `'${value.replace(/'/g, `'\\''`)}'`;
 }
@@ -1376,10 +1411,12 @@ ENVIRONMENTS
   (production→prd, sandbox→snd, staging→stg) but present uncertain mappings for confirmation.
   Before creating any asset, list product environments and require complete per-environment coverage.
   Missing environments can be created idempotently through the authenticated standalone CLI:
-    ductape_cli("products environments create <product-tag> -f <environment.json> --json")
+    ductape_cli("products environments create <product-tag> --env-file <environment.json> --json")
   The JSON requires env_name, description, and a three-character slug. The CLI fetches first, creates only
-  when absent, then fetches again to verify persistence. Update and verify with:
-    ductape_cli("products environments update <product-tag> <slug> -f <patch.json> --json")
+  when absent, then fetches again to verify persistence (with a short retry on the verification read to
+  absorb replication lag). No linked project is required — the product tag is always the explicit argument.
+  Update and verify with:
+    ductape_cli("products environments update <product-tag> <slug> --env-file <patch.json> --json")
   Export authenticated inventory with ductape_cli("products environments list <product-tag> --json"),
   save it as evidence, then reconcile locally:
     ductape_cli("migration-environments --analysis <analysis.json> --inventory <inventory.json> --strict --json")
@@ -4294,9 +4331,11 @@ const cliInputSchema = z.object({
         'Use this tool for administrative operations: creating or updating products, apps, ' +
         'resources (databases, storage, caches…), event broker topics, cloud connections, secrets, ' +
         'and for apply/migrate workflows.\n\n' +
-        'Note: environments, app actions, quotas, fallbacks, and jobs are configured in the ' +
-        'Workbench UI. Features also have no CLI creation command: define them in application code ' +
-        'with features.define so application boot/runtime registration makes them available.\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 ' +
+        '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.'),
 });
 async function loadMcpSdk() {
@@ -4748,15 +4787,16 @@ async function main() {
                 '    type field = "messageBrokers" (not "messagebrokers" or "events").\n' +
                 '    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 --tag <tag> --json" for compact inventory; use\n' +
-                '    "products components get --tag <tag> --type notifications|events --json" for focused detail.\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' +
                 '  - 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, app actions, auths, quotas, fallbacks, and jobs are configured ' +
-                'in the Workbench UI. Features have no CLI creation command because definitions are ' +
-                'code-first through features.define and registered by the application runtime.\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 ' +
+                '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 ' +
                 'covers runtime operations. Administrative operations will fail with "Authentication failed".\n\n' +
                 'The CLI uses the user\'s local logged-in session (ductape login). ' +

package/package.json

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