create-snipara 1.3.13 → 1.3.14

package/README.md

@@ -437,7 +437,7 @@ npx create-snipara print-config --json
 When testing a locally packed tarball, use `npm exec --package` instead of `npx`, for example:
 
 ```bash
-npm exec --package ./create-snipara-1.3.13.tgz create-snipara -- --help
+npm exec --package ./create-snipara-1.3.14.tgz create-snipara -- --help
 ```
 
 This avoids `npx` resolution issues with unpublished tarballs.

package/dist/index.js

@@ -9,7 +9,7 @@ import fs from "fs";
 import path from "path";
 import { execSync, spawn } from "child_process";
 import { homedir } from "os";
-var VERSION = "1.3.13";
+var VERSION = "1.3.14";
 var BASE_URL = "https://www.snipara.com";
 var API_URL = "https://api.snipara.com";
 var COMPANION_PACKAGE_NAME = "snipara-companion";
@@ -1694,13 +1694,12 @@ async function testHostedConnection(answers) {
         }
       ];
     }
-    const toolCount = toolsResponse.data.result?.tools?.length || 0;
-    spinner.succeed(`Connected! ${toolCount} MCP tools available.`);
+    spinner.succeed("Connected to Snipara Hosted MCP.");
     const checks = [
       {
         name: "hosted_connection",
         status: "pass",
-        detail: `tools/list succeeded (${toolCount} tools reported)`
+        detail: "tools/list succeeded"
       }
     ];
     const settingsResponse = await callHostedMcp(answers, "tools/call", {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-snipara",
-  "version": "1.3.13",
+  "version": "1.3.14",
   "description": "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   "main": "dist/index.js",
   "type": "module",