@techsologic/unolock-agent-mcp 0.1.12 → 0.1.13

package/README.md

@@ -134,6 +134,26 @@ npx @techsologic/unolock-agent-mcp --version
 
 The wrapper downloads the correct GitHub Release binary for the current platform on first use and then reuses the cached copy.
 
+The npm package is an OpenClaw-friendly install and launch path for the external UnoLock MCP binary.
+
+It is **not** an OpenClaw plugin package for `openclaw plugins install ...`.
+
+Project home:
+
+* `https://github.com/TechSologic/unolock-agent-mcp`
+
+Use it as a command that OpenClaw can launch, for example:
+
+```bash
+npx @techsologic/unolock-agent-mcp mcp
+```
+
+With no arguments, the npm wrapper starts the MCP server by default:
+
+```bash
+npx @techsologic/unolock-agent-mcp
+```
+
 ## Standalone config
 
 When the MCP runs outside the main UnoLock monorepo, it can usually derive its UnoLock runtime config from the UnoLock agent key connection URL. Environment variables and config files are primarily for overrides and custom deployments.

package/bin/unolock-agent-mcp.js

@@ -7,7 +7,7 @@ const path = require("path");
 const https = require("https");
 const { spawn } = require("child_process");
 
-const PACKAGE_VERSION = "0.1.12";
+const PACKAGE_VERSION = "0.1.13";
 const BINARY_VERSION = "0.1.11";
 const REPO = "TechSologic/unolock-agent-mcp";
 
@@ -108,7 +108,8 @@ async function ensureBinary() {
 
 async function main() {
   const dest = await ensureBinary();
-  const child = spawn(dest, process.argv.slice(2), {
+  const forwardedArgs = process.argv.length > 2 ? process.argv.slice(2) : ["mcp"];
+  const child = spawn(dest, forwardedArgs, {
     stdio: "inherit",
     env: process.env
   });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techsologic/unolock-agent-mcp",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "npx wrapper for the official UnoLock Agent MCP release binaries",
   "license": "SEE LICENSE IN README.md",
   "homepage": "https://github.com/TechSologic/unolock-agent-mcp",