yaver-cli 1.95.6 → 1.95.7

package/bin/yaver-mcp

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+// yaver-mcp — one-shot entry point that launches the Yaver MCP stdio
+// server. Equivalent to running `yaver mcp`, but exposed as its own
+// bin so MCP clients + the MCP Registry can invoke it as
+//
+//   npx -y yaver-cli yaver-mcp
+//
+// or by adding `"command": "yaver-mcp"` directly to their mcpServers
+// config (once yaver-cli is installed globally). Forwards any extra
+// arguments transparently.
+
+const { runUnified } = require('../src/index');
+
+runUnified(['mcp', ...process.argv.slice(2)]);

package/package.json

@@ -1,10 +1,13 @@
 {
   "name": "yaver-cli",
-  "version": "1.95.6",
+  "version": "1.95.7",
+  "mcpName": "io.github.kivanccakmak/yaver",
   "description": "Unified npm bootstrap for the Yaver agent and push-to-device React Native tooling",
   "bin": {
     "yaver": "bin/yaver",
-    "yaver-push": "bin/yaver-push"
+    "yaver-push": "bin/yaver-push",
+    "yaver-mcp": "bin/yaver-mcp",
+    "yaver-cli": "bin/yaver-mcp"
   },
   "main": "src/index.js",
   "files": [

package/src/preuninstall.js

@@ -0,0 +1,23 @@
+#!/usr/bin/env node
+// npm preuninstall hook — best-effort call to `yaver mcp unregister` so the
+// CLI cleans up the MCP entries it added to Claude Desktop / Claude Code /
+// Codex / Cursor / VS Code / Windsurf / Zed before the binary is removed.
+//
+// Must NEVER fail the uninstall. If yaver is not on PATH, silently succeed.
+
+const { spawnSync } = require("node:child_process");
+
+try {
+  const res = spawnSync("yaver", ["mcp", "unregister"], {
+    stdio: "inherit",
+    timeout: 15_000,
+  });
+  if (res.error && res.error.code === "ENOENT") {
+    // yaver not on PATH — nothing to clean up.
+    process.exit(0);
+  }
+  // Ignore exit code; we always succeed so npm uninstall can finish.
+  process.exit(0);
+} catch {
+  process.exit(0);
+}