@modeltoolsprotocol/mtpcli 0.2.0 → 0.2.2

package/README.md

@@ -6,7 +6,7 @@ The command-line interface for the [Model Tools Protocol](https://github.com/mod
 
 LLM agents need to discover and use tools. Right now there are two worlds:
 
-**CLI tools** are the backbone of software development. They're composable (`|`), scriptable, version-controlled, and work everywhere. But LLMs can't discover what a CLI does -they have to parse `--help` text, guess at arguments, and hope for the best.
+**CLI tools** are the backbone of software development. They're composable (`|`), scriptable, version-controlled, and work everywhere. But LLMs can't discover what a CLI does - they have to parse `--help` text, guess at arguments, and hope for the best.
 
 **MCP (Model Context Protocol)** solves discovery beautifully. Tools declare typed schemas, and LLM hosts discover them via a structured handshake. But MCP requires running a server process, speaking JSON-RPC over stdio/SSE, and building within the MCP ecosystem. Your existing CLI tools don't get any of this for free.
 

package/dist/index.js

@@ -7917,17 +7917,38 @@ function sendNotification(writer, method, params) {
   writer.write(JSON.stringify(req) + `
 `);
 }
-async function readResponse(rl) {
-  for await (const line of rl) {
-    const trimmed = line.trim();
-    if (!trimmed)
-      continue;
-    const msg = JSON.parse(trimmed);
-    if ("id" in msg && msg.id !== undefined) {
-      return JsonRpcResponseSchema2.parse(msg);
-    }
-  }
-  throw new Error("MCP server closed connection");
+function readResponse(rl) {
+  return new Promise((resolve, reject) => {
+    const onLine = (line) => {
+      const trimmed = line.trim();
+      if (!trimmed)
+        return;
+      let msg;
+      try {
+        msg = JSON.parse(trimmed);
+      } catch (e) {
+        rl.off("line", onLine);
+        rl.off("close", onClose);
+        reject(e);
+        return;
+      }
+      if ("id" in msg && msg.id !== undefined) {
+        rl.off("line", onLine);
+        rl.off("close", onClose);
+        try {
+          resolve(JsonRpcResponseSchema2.parse(msg));
+        } catch (e) {
+          reject(e);
+        }
+      }
+    };
+    const onClose = () => {
+      rl.off("line", onLine);
+      reject(new Error("MCP server closed connection"));
+    };
+    rl.on("line", onLine);
+    rl.on("close", onClose);
+  });
 }
 var init_mcp = __esm(() => {
   init_models();
@@ -9187,7 +9208,7 @@ function cleanJson(obj) {
 }
 
 // src/index.ts
-var VERSION3 = "0.2.0";
+var VERSION3 = "0.2.2";
 function selfDescribe() {
   const schema = {
     name: "mtpcli",
@@ -9334,23 +9355,23 @@ function selfDescribe() {
       },
       {
         name: "serve",
-        description: "Serve CLI tools as an MCP server over stdio",
+        description: "Serve CLI tools as an MCP server over stdio. Not meant to be run directly; add to your MCP client config instead.",
         args: [
           {
             name: "--tool",
             type: "array",
             required: true,
-            description: "Tool name(s) to serve"
+            description: "Tool name(s) to serve (must support --describe)"
           }
         ],
         examples: [
           {
-            description: "Serve a single tool",
-            command: "mtpcli serve --tool filetool"
+            description: "Add to ~/.claude.json as an MCP server",
+            command: '{ "mcpServers": { "my-tools": { "type": "stdio", "command": "mtpcli", "args": ["serve", "--tool", "my-cli-tool"] } } }'
           },
           {
-            description: "Serve multiple tools",
-            command: "mtpcli serve --tool filetool --tool mytool"
+            description: "Serve multiple tools in one MCP server",
+            command: '{ "mcpServers": { "my-tools": { "type": "stdio", "command": "mtpcli", "args": ["serve", "--tool", "tool1", "--tool", "tool2"] } } }'
           }
         ]
       },
@@ -9520,7 +9541,42 @@ authCmd.command("refresh").description("Force-refresh the stored OAuth token for
   const { runRefresh: runRefresh2 } = await Promise.resolve().then(() => (init_auth(), exports_auth));
   await runRefresh2(tool);
 });
-program2.command("serve").description("Serve CLI tools as an MCP server (cli2mcp bridge)").requiredOption("--tool <names...>", "Tool(s) to serve").action(async (opts) => {
+program2.command("serve").description("Serve CLI tools as an MCP server (cli2mcp bridge)").requiredOption("--tool <names...>", "Tool(s) to serve").addHelpText("after", `
+This command is meant to be used as an MCP server, not run directly.
+Add it to your MCP client config (e.g. ~/.claude.json):
+
+  {
+    "mcpServers": {
+      "my-tools": {
+        "type": "stdio",
+        "command": "mtpcli",
+        "args": ["serve", "--tool", "my-cli-tool"]
+      }
+    }
+  }
+
+Any CLI tool on your PATH that supports --describe can be served.
+Multiple tools can be combined into a single MCP server:
+
+  mtpcli serve --tool tool1 --tool tool2`).action(async (opts) => {
+  if (process.stdin.isTTY) {
+    process.stderr.write(`Error: 'mtpcli serve' is an MCP server and should not be run directly.
+` + `Add it to your MCP client config instead. For example, in ~/.claude.json:
+
+` + `  {
+` + `    "mcpServers": {
+` + `      "my-tools": {
+` + `        "type": "stdio",
+` + `        "command": "mtpcli",
+` + `        "args": ["serve", "--tool", ${JSON.stringify(opts.tool[0] ?? "my-cli-tool")}]
+` + `      }
+` + `    }
+` + `  }
+
+` + `Run 'mtpcli serve --help' for more details.
+`);
+    process.exit(1);
+  }
   const { run: run5 } = await Promise.resolve().then(() => (init_serve(), exports_serve));
   await run5(opts.tool);
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@modeltoolsprotocol/mtpcli",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "license": "Apache-2.0",
   "type": "module",
   "bin": {