Create Fibery CLI

Ideas & Features
1

I think a useful addition to Fibery would be a CLI. Mainly because of two reasons (where reason #1 is the most important IMO):

  1. We are seeing a bit of a shift from MCP towards CLI in a lot of places. Probably because it’s a bit more token efficient and requires less context use. OpenClaw is one of the popular examples that swear by the CLI approach.
    Providing Fibery CLI could be a great new way for AI agents to interact with Fibery in an efficient way.
  2. A CLI enables native shell scripting and CI/CD integration. Teams could trigger Fibery actions directly from GitHub Actions, deployment pipelines, or cron jobs. While still keeping automation lightweight and composable with standard Unix tooling.

(Have not tried this tool but maybe it could be useful: GitHub - philschmid/mcp-cli: Lighweight CLI to interact with MCP servers · GitHub)

2

I heard about this on a podcast recently for building cli tools: GitHub - HKUDS/CLI-Anything: CLI-Anything: Making ALL Software Agent-Native -- CLI-Hub: https://clianything.cc/ · GitHub

1 Like
3

This one is really nice!