v2.24.0

Superseded. The work-plane half of the roster described here was removed in v2.54.0. The unified MCP itself is unchanged; only the tool counts and the work tools are historical.

Release notes for orun v2.24.0.

Highlights

• One binary, one MCP. orun mcp serve is now the ecosystem's unified local MCP server: the platform tool plane — 25 tools over the Orun Cloud public API (catalog, runs and logs, audit, events, access, usage, billing, config, secret metadata, webhooks) — lands natively in the binary and mounts alongside the 9 work-plane tools. One stdio connection, 34 tools, gated by what the context supports: platform tools whenever auth resolves, work tools when a workspace scope resolves.
• orun mcp tools. Print the merged roster — provider and read-only columns, --json for scripting — without starting a server.
• --read-only. Serve the platform plane's 19 reads only: the 6 platform writes are filtered from tools/list and blocked at execution. Work tools are mutator-shaped by design and unaffected.
• Write rails. Every platform write carries a per-attempt Idempotency-Key (retries replay instead of duplicating; supply your own idempotencyKey to control it), every platform call is stamped x-client-surface: mcp for audit provenance, and member_invite never returns the invitation's one-time accept token. Availability is gated by the workspace's feature.mcp_server entitlement (fail-open).
• One contract, two implementations. The 25 platform tools are pinned — names, schemas, annotations — to a vendored manifest exported from the hosted remote MCP server (Streamable HTTP, part of Orun Cloud), enforced by a parity test in CI. Prompts and docs are portable between the local and remote surfaces.

New: the unified MCP

orun auth login
claude mcp add orun -- orun mcp serve

orun mcp tools | wc -l   ->  35   # header + 9 work + 25 platform

Surface	Tools	Mounts when
Work plane	9 (5 reads, 4 mutator writes)	a workspace scope resolves
Platform plane	25 (19 reads, 6 gated writes)	cloud auth resolves

• Platform tools take an explicit workspace argument; serve's resolved scope fills it by default (explicit input wins).
• Tool failures are structured isError verdicts preserving the platform error code (forbidden, not_found, rate_limited, …), never protocol faults.
• Connecting from the hosted side instead? Your workspace console's Connect page has the same snippets pointing at orun mcp serve.

See orun mcp for the full roster and client setup.

Compatibility

• serverInfo renamed: orun-work → orun. The unified server identifies itself as orun in the MCP initialize response. Client configuration (the name you registered the server under) is unaffected, but anything scripted against serverInfo.name must update.
• Existing work-MCP clients keep working unchanged: the 9 work tools keep their names, schemas, and semantics, and orun mcp serve --workspace … behaves as before — it simply advertises the platform tools too.
• The structural work-plane invariants hold over the merged roster: no status tool, no pin tool, no lifecycle tool — asserted by test across all 34 tools.