Actions and MCP commands in the CLI
What it does
The CLI gained an action creation wizard, action manifests, connect-variable flags, and commands for MCP servers — plus custom page and portal commands the following week.
Before this
An expansion of a CLI that was a week old. It could already build agents and deployments, but actions and MCP servers still had to be set up by clicking.
Why it matters
Integration setup becomes something you can check into a repo and replay, rather than a sequence of clicks you have to remember.
How it works
The additions were mostly about integrations becoming reproducible: an action creation wizard, action manifests, connect-variable flags for wiring credentials, and commands for MCP servers — with custom page and portal commands following the week after.
A manifest is the piece that changes the workflow. Integration setup stops being a sequence of clicks you have to remember and becomes a file you can check into a repo, review, and replay into another workspace.