Salus MCP v0.18.0 — rollbacks, security insight, and safer agent deploys

Salus MCP v0.18.0 gives your AI agents — and the developers working alongside them — a much richer, safer set of tools for operating on Salus directly from their environment. This release adds real operational muscle (rollbacks, security posture, environment management) and makes the whole surface more honest and harder to trip over.

New tools and capabilities

• Rollback a deployment — list previous revisions and roll a deployment back to a known-good one, without leaving your agent or editor (list_deployment_revisions, rollback_deployment).
• Security insight — an org-wide activity feed (list_organization_events) and per-deployment vulnerability posture (get_environment_vulnerabilities), so an agent can answer “what changed?” and “are we exposed?” on the spot.
• Level-aware environment variables — manage variables across organisation, space, project, and release-config levels, with a merged hierarchy and override view so it’s always clear which value wins and why.
• Rotate database passwords — keep credentials fresh directly through MCP.
• Sign out — auth_logout revokes the session and clears the local token.

Truthful pipeline status

Advisory, non-blocking stage failures are now distinguishable from real ones. Pipelines report completedWithWarnings, and stages and tasks carry an allowedToFail flag — so a failed, non-blocking security scan no longer reads as a broken deploy. Your agents get an accurate picture of what actually happened.

Reliability and clearer errors

• Hardened login — MCP skips re-login when you’re already authenticated, tolerates concurrent sign-ins without clashing, and only surfaces the manual URL if the browser didn’t open on its own.
• Clear “can’t reach Salus” messaging — network, proxy, and VPN blocks now produce a plain, actionable message instead of a cryptic failure.
• Clearer tool names and descriptions — reworked to reduce agent confusion, with read-only and destructive-action safety hints surfaced per tool so agents (and you) know what’s safe before acting.

Distribution and internals

• Nightly canary channel — a new pre-release MCP build, wired to production and built continuously from main, for teams who want the latest ahead of a stable release.
• MCP core as a standalone package — the MCP core is now split out from the CLI as @salus-cloud/mcp-core.
• Deep links to affected resources — enterprise events and results now link straight to the resources they created or affected, and user-facing copy has been cleaned up throughout.

---

Update to v0.18.0 to pick these up. As always, we’d love to hear what you think — your feedback shapes what we build next.