Add --version flag to xcrs and document cargo install
xcrs previously had no --version flag; `xcrs --version` errored. Add `#[command(version)]` so it reports its crate version, matching `smb` and the version recorded in the MCP registry. Also document that `xcrs` is installed via `cargo install xcrs` from crates.io, not Homebrew, since `brew install smbcloud-cli` ships only the `smb` binary. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Seto Elkahfi committed
Aug 3, 2026 at 11:10 UTC
888debee0077a32b10f4680c28a17caf88385ae6
2 files changed
+7
crates/xcrs/src/main.rs
+1
@@ -5,6 +5,7 @@ use xcrs::{IosAppTest, XcodeCommandLineTools};
5
6
#[derive(Debug, Parser)]
7
#[command(name = "xcrs")]
8
+#[command(version)]
9
#[command(about = "Cross-platform mobile and TV app automation")]
10
struct Cli {
11
/// Run as a standalone Model Context Protocol server over stdio.
docs/mcp.md
+6
@@ -259,6 +259,12 @@ smb --mcp --scope automation
259
xcrs --mcp
260
```
261
262
+> **Installing `xcrs`:** the standalone binary is published to
263
+> [crates.io](https://crates.io/crates/xcrs) — install it with
264
+> `cargo install xcrs`. It is **not** distributed through Homebrew; `brew
265
+> install smbcloud-cli` only provides the `smb` binary (use `smb --mcp --scope
266
+> automation` for the same tools without a separate install).
267
+
268
Both commands expose the same target-aware tools with the same names. Tool
269
names do not repeat the server brand because MCP clients already namespace
270
them by server.