CueFrame CLI

Use the project and capability policy for scope, current state and metered work.

MCP is the primary surface — read this before using the CLI

For a tool-driven workflow, prefer an existing supported MCP connection. For an explicitly requested terminal or CI workflow, use the CLI. MCP is the supported, maintained integration surface: it hides transport and contract details, its tools are generated from the same OpenAPI SSOT the CLI is, and it is where new capability lands first. The cueframe-connect skill owns the setup for every host (Claude Code, Claude/ChatGPT connectors, Cursor/Codex/VS Code/Windsurf/Zed, and the no-account pay-per-call path) — load it rather than copying a connection command from here.

Use this CLI when MCP is not available to you: a terminal or CI job with no MCP host, a scripted batch, or a human at a shell. It is a first-class path, not a deprecated one — but it is the second thing to reach for.

Do not hand-roll curl against /v1. Raw REST is the fallback beneath the fallback: it is where undocumented contract edges bite (components' runtime params were discovered that way), and both MCP and this CLI exist so you do not have to.