flowviant 0.31.1 → 0.32.0

package/bin/cli.mjs

@@ -114,6 +114,15 @@ if (process.argv[2] === 'shot') {
 // `flowviant env <import|set|show>` — the CLI half of team env sync. Values
 // are sealed to the project pubkey ON THIS MACHINE (same write-only crypto as
 // the browser); `show` decrypts locally — it only works on an ENROLLED machine.
+// `flowviant mcp` — connect YOUR Claude to Flowviant so you can file work from
+// the terminal. Mints a `cli` credential: a separate principal from the build
+// workers, with only the management tools and no way to claim or ship work.
+if (process.argv[2] === 'mcp') {
+  const { runMcpCommand } = await import('./lib/mcp-cli.mjs');
+  await runMcpCommand(process.argv.slice(3));
+  process.exit(0);
+}
+
 if (process.argv[2] === 'env') {
   const { runEnvCommand } = await import('./lib/env-cli.mjs');
   await runEnvCommand(process.argv.slice(3));

package/bin/lib/mcp-cli.mjs

@@ -0,0 +1,83 @@
+/**
+ * `flowviant mcp` — connect YOUR Claude to Flowviant so you can file work from
+ * the terminal ("stick that on the board", "file a task for this TODO").
+ *
+ * This mints a `cli` credential, which is a different principal from the worker
+ * tokens the daemon rotates for builds. That separation is the point, not
+ * bookkeeping: a worker reads untrusted repo, PR and issue text all day, so
+ * giving THAT principal tools that write to your workspace would mean a hostile
+ * string in a README could file work as you. The cli credential sees only the
+ * management tools and can never claim or complete work; the worker can never
+ * reach create_task.
+ *
+ * There is deliberately no invite capability on it. Invites grant access to a
+ * paid workspace and are guarded by a human browser session; you ask Flowvy in
+ * the app for those, and approve the card.
+ */
+
+import { FLEET_TOKEN, USER_AGENT, MCP_URL, FLEET_URL } from './config.mjs';
+
+const CLI_TOKEN_URL = FLEET_URL.replace(/\/agents\/?$/, '/cli-token');
+
+export async function runMcpCommand(args = []) {
+  if (!FLEET_TOKEN) {
+    console.error(
+      'error: no credential. Run `flowviant login` first — this needs the\n' +
+        'fleet credential the daemon uses, so it knows which project to connect.'
+    );
+    process.exit(1);
+  }
+
+  let res;
+  try {
+    res = await fetch(CLI_TOKEN_URL, {
+      method: 'POST',
+      headers: {
+        authorization: `Bearer ${FLEET_TOKEN}`,
+        'content-type': 'application/json',
+        'user-agent': USER_AGENT,
+      },
+    });
+  } catch (err) {
+    console.error(`error: could not reach Flowviant (${err?.message || err})`);
+    process.exit(1);
+  }
+
+  if (!res.ok) {
+    console.error(
+      `error: could not mint a CLI credential (${res.status}). ` +
+        (res.status === 401 || res.status === 403
+          ? 'Your credential may have been revoked — try `flowviant login` again.'
+          : 'Try again in a moment.')
+    );
+    process.exit(1);
+  }
+
+  const body = await res.json().catch(() => null);
+  const token = body?.data?.token;
+  if (!token) {
+    console.error('error: Flowviant returned no token. Try again.');
+    process.exit(1);
+  }
+
+  const cmd =
+    `claude mcp add --transport http flowviant ${MCP_URL} ` +
+    `--header "Authorization: Bearer ${token}"`;
+
+  // --print for piping into a shell; otherwise explain what this does, since
+  // pasting a credential into a command deserves a sentence of context.
+  if (args.includes('--print')) {
+    console.log(cmd);
+    return;
+  }
+
+  console.log('');
+  console.log('Run this to connect your Claude to Flowviant:');
+  console.log('');
+  console.log(`  ${cmd}`);
+  console.log('');
+  console.log('Then, in any Claude session: "file a task in Flowviant for …".');
+  console.log('Tasks land as drafts — nothing runs until you open one in the');
+  console.log('app and @mention an agent.');
+  console.log('');
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flowviant",
-  "version": "0.31.1",
+  "version": "0.32.0",
   "description": "Run your own Claude Code as headless build agents for Flowviant — on your own credentials. Claims dispatched work, opens PRs, captures review evidence, and routes questions back to you.",
   "type": "module",
   "bin": {