@modeltoolsprotocol/mtpcli 0.3.0 → 0.3.1

package/README.md

@@ -6,26 +6,20 @@ 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.
-
-These are both good ideas with real tradeoffs:
+**MCP (Model Context Protocol)** solves discovery beautifully. Tools declare typed schemas, and LLM hosts discover them via a structured handshake. But MCP tools aren't composable. Each invocation goes through the model. You can't pipe one MCP tool's output into another. You can't script them without an LLM in the loop.
 
 | | CLI tools | MCP tools |
 |---|---|---|
-| **Composability** | First-class. Pipes, shell scripts, xargs -50 years of Unix | Requires an orchestrator or agent framework |
+| **Composability** | First-class. Pipes, shell scripts, xargs. 50 years of Unix | Requires an orchestrator or agent framework |
 | **Discovery** | Poor. Parse `--help` and hope | Excellent. Typed schemas via handshake |
 | **Runtime** | Any shell, anywhere | Needs an MCP host (Claude Desktop, etc.) |
 | **Deployment** | `brew install`, `cargo install`, a binary in PATH | Run a server process, configure the host |
 | **Interop** | Pipes to anything | Talks to MCP clients only |
-| **Scriptable without an LLM** | Yes -that's the whole point of CLIs | Not really -designed for LLM interaction |
-| **Streaming / subscriptions** | Limited (stdout streaming) | Built-in (SSE, notifications) |
-| **Stateful interaction** | Stateless by design (each invocation is fresh) | Stateful sessions with context |
+| **Scriptable without an LLM** | Yes, that's the whole point of CLIs | Not really, designed for LLM interaction |
 | **Adoption cost** | One flag/decorator | New protocol, server scaffolding, SDK |
 
-MCP is the right choice when you need stateful sessions, streaming, or deep integration with an LLM host. CLIs are the right choice when you want composability, scriptability, and zero infrastructure.
-
 The gap is discovery. `mtpcli` fills it.
 
 ## Install
@@ -34,8 +28,52 @@ The gap is discovery. `mtpcli` fills it.
 npm install -g @modeltoolsprotocol/mtpcli
 ```
 
+## What it does
+
+**mtpcli** bridges the gap between CLI tools and MCP servers. It turns any `--describe` CLI into an MCP server, turns any MCP server into a composable CLI, and handles discovery, auth, and validation along the way.
+
 ## Usage
 
+### Serve CLI tools over MCP
+
+Any CLI that supports `--describe` becomes an MCP server:
+
+```bash
+$ mtpcli serve --tool atlasctl --tool mytool
+
+mtpcli serve: serving 6 tool(s) from 2 CLI tool(s)
+  - atlasctl__confluence page get
+  - atlasctl__config set
+  - atlasctl__config get
+  - mytool__convert
+  ...
+```
+
+Drop it into your Claude Desktop config and it works like any other MCP server. The bridge reads `--describe`, translates commands to MCP tools, and shells out to the real CLI when the host calls a tool.
+
+### Wrap an MCP server as a CLI
+
+Atlassian ships an MCP server at `mcp.atlassian.com`. With `mtpcli wrap`, it's a CLI:
+
+```bash
+# Discover what tools the server offers
+$ mtpcli wrap --url "https://mcp.atlassian.com/v1/mcp" --describe
+
+# Fetch a Confluence page
+$ mtpcli wrap --url "https://mcp.atlassian.com/v1/mcp" \
+    getConfluencePage -- --cloudId "$CLOUD_ID" --pageId 12345 --contentFormat markdown
+
+# Pipe it into jq, grep, or anything else
+$ mtpcli wrap --url "https://mcp.atlassian.com/v1/mcp" \
+    getConfluencePage -- --cloudId "$CLOUD_ID" --pageId 12345 --contentFormat markdown \
+    | jq -r '.body'
+
+# Works with stdio servers too
+$ mtpcli wrap --server "npx @mcp/server-github" --describe
+```
+
+The 2,500+ MCP servers people have built? They're all CLI tools now. Pipe their output, use them in scripts, compose them with other tools.
+
 ### Search for tools and commands
 
 ```bash
@@ -52,7 +90,7 @@ mtpcli search --scan-path "git commit"
 ### Authenticate with a tool
 
 ```bash
-# OAuth2 login
+# OAuth2 login (opens browser, handles callback)
 mtpcli auth login mytool
 
 # API key / bearer token login
@@ -68,22 +106,7 @@ eval $(mtpcli auth env mytool)
 mtpcli auth logout mytool
 ```
 
-### Serve tools over MCP
-
-```bash
-# Start an MCP server that bridges describe-compatible tools
-mtpcli serve --tool mytool --tool anothertool
-```
-
-### Wrap an MCP server as a CLI
-
-```bash
-# Describe an MCP server's tools
-mtpcli wrap --server "npx @mcp/server-github" --describe
-
-# Call a tool on an MCP server
-mtpcli wrap --server "npx @mcp/server-github" search_repos -- --query mtpcli
-```
+See [AUTH.md](AUTH.md) for details on token storage, usage patterns, and bridge integration.
 
 ### Validate a tool's --describe output
 
@@ -114,7 +137,7 @@ mtpcli completions fish mytool | source
 ### Describe self
 
 ```bash
-# Output mtpcli's own describe schema (JSON)
+# mtpcli is itself an MTP-compliant tool
 mtpcli --describe
 ```
 

package/dist/index.js

@@ -10564,7 +10564,7 @@ function cleanJson(obj) {
 }
 
 // src/index.ts
-var VERSION3 = "0.3.0";
+var VERSION3 = "0.3.1";
 function selfDescribe() {
   const schema = {
     name: "mtpcli",

package/package.json

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