AdviblyDocs

The Advibly CLI

Advibly from a terminal - install, log in, and make something.

advibly is Advibly from a shell script. Every command is a tool of the MCP server, so anything an agent can do, you can do from a terminal: brands, assets, image, video and audio generation, projects, social publishing.

Use the CLI when a workflow starts with local files, must write results to disk, or belongs in a script. Use MCP directly when the work is being planned and reviewed inside an agent conversation.

Install

npm i -g advibly

Or run it without installing:

npx advibly <command>

Needs Node 20 or later, and an Advibly account.

Connect

advibly login

This opens a browser for the same OAuth flow Claude Code and Cursor use. Tokens are stored in ~/.config/advibly with owner-only permissions. There is no API key to manage.

advibly whoami     # confirm who you are signed in as
advibly logout     # sign out of this server (--all for every profile)

The connection is ready when advibly whoami prints the intended account and advibly list-brands returns its brands.

Make something

advibly list-brands
advibly config set brand_id <id>
advibly generate-image --prompt "..." --aspect-ratio 4:5

Setting brand_id as a default once saves passing it to every subsequent command. See Configuration.

The generation command waits for a terminal result by default. A successful run ends with exit code 0 and prints the completed result; use --json when a script will consume it.

Move files

The two things a CLI can do that an agent cannot:

advibly upload ./product.png              # local file -> brand asset library
advibly download <generation-id> -o ./out # results -> disk

It is an MCP client, not a second API

The CLI speaks to https://advibly.com/mcp and turns the server's tools/list into subcommands. advibly_generate_image becomes advibly generate-image, and each argument becomes a flag (brand_id--brand-id).

The practical consequence: a new tool becomes a new command with no CLI upgrade. The list is refreshed on login and with advibly tools --refresh.

Credits

Generation commands spend the connected account's credits. Read-only and organisational MCP tools do not.

advibly check-credits
advibly buy-credits

Before a batch, check the balance once and estimate the number of billable generation calls. A failed or rejected generation is refunded automatically.

On this page