TL;DR: Catch-up since the v0.2.0 post. mcp-better is 0.4.2 — still the small BETTER textbook for modern MCP (AGENTS.md · NONE | GOOD | [BETTER] | BEST). Cargo first · npx now available option — same Rust binary either way.

cargo install mcp-better --version 0.4.2 npx mcp-better@0.4.2

What happened since 0.2.0

One blog, one arc — no post per patch. Short tour from the last write-up to today:

  • 0.3 — tighter tests and a real textbook tree shipped with the app
  • 0.4 — dual package: cargo first, npm added as a second path to the same binary
  • 0.4.1 / 0.4.2 — registry dual clean · OIDC releases (no long-lived tokens)

Still 7/28, still health + echo, still stdio by default. Cargo path unchanged; npx is the new option for hosts that already speak npm.

Why add npx?

Cargo first — always was. Lots of MCP docs only show npx, though. Dual-package means that path starts the same native binary, not a rewrite in JavaScript.

If you live in cargo-land, keep using cargo. If your host only knows npm, you have an option now.

Try it

cargo install mcp-better --version 0.4.2 mcp-better --help npx mcp-better@0.4.2

More depth: why dual-package · how to ship one · origin post (v0.2).

Technical details

  • Version: 0.4.2 (August 8, 2026)
  • Protocol: 2026-07-28 (7/28)
  • Identity: io.github.Wolfe-Jam/mcp-better
  • Packages: crates.io + npm mcp-better (same version)
  • Tools @ 0.4.2: health, echo
  • Transports: stdio default · --http local demo only
  • 0.4.0: npm shim downloads GH Release binary · dual server.json · three-file lockstep
  • 0.4.1: npm mcpName for dual registry publish
  • 0.4.2: OIDC Trusted Publishing (crates + npm on tag)
  • Ladder: NONE | GOOD | [BETTER] | BEST — textbook for AGENTS.md

Built with .faf ☑️ Same binary either way. 🏎️