@modeltoolsprotocol/mtpcli 0.3.3 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -19
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,25 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
The command-line interface for the [Model Tools Protocol](https://github.com/modeltoolsprotocol/modeltoolsprotocol) (MTP). Discover, authenticate, and bridge tools that implement the `--describe` convention.
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
LLM agents need to discover and use tools. Right now there are two worlds:
|
|
8
|
-
|
|
9
|
-
**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.
|
|
10
|
-
|
|
11
|
-
**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.
|
|
12
|
-
|
|
13
|
-
| | CLI tools | MCP tools |
|
|
14
|
-
|---|---|---|
|
|
15
|
-
| **Composability** | First-class. Pipes, shell scripts, xargs. 50 years of Unix | Requires an orchestrator or agent framework |
|
|
16
|
-
| **Discovery** | Poor. Parse `--help` and hope | Excellent. Typed schemas via handshake |
|
|
17
|
-
| **Runtime** | Any shell, anywhere | Needs an MCP host (Claude Desktop, etc.) |
|
|
18
|
-
| **Deployment** | `brew install`, `cargo install`, a binary in PATH | Run a server process, configure the host |
|
|
19
|
-
| **Interop** | Pipes to anything | Talks to MCP clients only |
|
|
20
|
-
| **Scriptable without an LLM** | Yes, that's the whole point of CLIs | Not really, designed for LLM interaction |
|
|
21
|
-
| **Adoption cost** | One flag/decorator | New protocol, server scaffolding, SDK |
|
|
22
|
-
|
|
23
|
-
The gap for CLIs is discovery. `mtpcli` fills it.
|
|
5
|
+
CLI tools are composable but not LLM-discoverable. MCP tools are discoverable but not composable. MTP bridges the gap with a single `--describe` flag. See the [protocol README](https://github.com/modeltoolsprotocol/modeltoolsprotocol) for the full rationale.
|
|
24
6
|
|
|
25
7
|
## Install
|
|
26
8
|
|
package/dist/index.js
CHANGED
|
@@ -10954,7 +10954,7 @@ function selfDescribe() {
|
|
|
10954
10954
|
};
|
|
10955
10955
|
console.log(JSON.stringify(cleanJson(schema), null, 2));
|
|
10956
10956
|
}
|
|
10957
|
-
var VERSION = "
|
|
10957
|
+
var VERSION = "1.1.0", program2, authCmd;
|
|
10958
10958
|
var init_src = __esm(async () => {
|
|
10959
10959
|
init_esm();
|
|
10960
10960
|
init_models();
|