Skip to main content
Show CLI, M4L bridge, and Python bridge versions.

​
Command line

​
version

Show Vibrai CLI, M4L bridge, and Python bridge versions

​
MCP tools

​
get_version

Get the running Vibrai.Mcp server version (assembly) and the M4L bridge version (package.json), plus a best-effort license block (status, features_enabled, days_remaining). Bridge probes are best-effort and always classified: bridge_status and python_bridge_status read “ok” (with probe timings) on success or a failure kind (unreachable/timed_out/error, unavailable) without ever hanging. When both bridges are healthy, note explains that a tool call hanging alongside a successful probe indicates an MCP client-transport fault, not a bridge problem. Also reports every other shipped component so nothing goes unmentioned: mcp_server_version/mcpb_bundle_version (read from the installed Vibrai.mcpb manifest — the only signal available for “what will Claude Desktop run”), mcp_binary_version/mcp_binary_status (read directly off this process’s own Vibrai.Mcp binary via FileVersionInfo — a distinct, bundle-independent signal; a packaging self-check against mcp_version), amxd_device_status (a content-hash compare of the installed vibrai.amxd against this server’s shipped copy: matches_shipped/stale/not_installed/shipped_source_missing), templates_status (same hash compare; templates_versioned is always false — Ableton .als files carry no internal version stamp), and remote_script_status (same hash compare against the installed Python remote-script package — distinguishes “never installed” from “installed but Live is shut”, which python_bridge_status alone cannot). mcpb_bundle_drift is a warning string (or null) when the staged .mcpb reports a different Vibrai than this server, with its own remedy — re-drag it into Claude Desktop and restart that app, not Ableton Live.