[Feature Request]: Client CLI

[gabe-l-hart]

🧭 Type of Feature

Please select the most appropriate category:

• [ ] Enhancement to existing functionality
• [x] New feature or capability
• [ ] New MCP-compliant server
• [ ] New component or integration
• [x] Developer tooling or test improvement
• [ ] Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)
• [ ] Other (please describe below)

🧭 Epic

Title: Client CLI for managing CF components Goal: With CF running locally, developers would be able to perform all of the actions currently hosted by the UI/REST API via a CLI Why now:

• This is part of the effort to make CF a daily-driver component in the agentic developer workflow. First-class CLI experiences are common-place with the most popular open-source AI developer tools (ollama, lmstudio, continue.dev, etc), so providing a client CLI would bring this familiar look-and-feel and help encourage developers to adopt CF for their daily work.
• Having a client CLI would also allow seamless transition between a local and hosted instance.

📐 Design Sketch (optional)

Include a diagram, sketch, or flow (use Mermaid if desired):

(TODO: working on a diagram with the CLI actions)

---

🔗 MCP Standards Check

• [x] Change adheres to current MCP specifications
• [x] No breaking changes to existing MCP-compliant integrations
• [ ] If deviations exist, please describe them below:

---

🔄 Alternatives Considered

List any alternative designs, existing workarounds, or rejected ideas.

---

📓 Additional Context

Include related issues, links to discussions, issues, etc.