Slima MCP

Why `slima-mcp@0`: version-pinning explained

약 3분 소요

Every example uses slima-mcp@0 — that @0 is an npm semver major-version pin. Why:

Slima Authorized Apps: slima-mcp@0 version-pinning strategy affects connection stability for clients listed here

Three forms compared

Form Resolves to
slima-mcp Latest (including breaking changes)
slima-mcp@0 Latest 0.x.x (won't cross into 1.0)
[email protected] Exact version

Why @0 is recommended

The balance:

  • Auto-take patches (bug fixes): 0.5.1 → 0.5.2 automatic
  • Auto-take minors (features): 0.5.x → 0.6.x automatic
  • Don't get surprised by 1.0 breaking changes

When 1.0 ships

When slima-mcp cuts 1.0:

  • Your config says slima-mcp@0 → stays on 0.x
  • You change config to slima-mcp@1 → opts into 1.0
  • The README + Slima docs explain 0.x → 1.0 migration

What npx -y does

npx -y slima-mcp@0
  • npx = run an npm package without installing globally
  • -y = auto-accept the download prompt
  • slima-mcp@0 = package + version range

Each run checks the latest 0.x and downloads as needed.

Lock to an exact version

For reproducibility (e.g. production CI):

"args": ["-y", "[email protected]"]

For daily dev: @0 is better.

Related

Was this helpful?