The Pliris CLI

Work with your catalog from the terminal — list bands and songs, ask questions in plain English, and build Ableton sets, all scriptable with --json.

The pliris command-line tool gives you your whole From Studio to Stage catalog from the terminal — list bands, search songs, ask questions in plain English, and kick off cloud Ableton builds. It talks to the same server as the MCP / AI-assistant surface and runs with the exact permissions of your account.

Install

npx @fromstudiotostage/pliris --help      # no install
npm install -g @fromstudiotostage/pliris  # or install globally

Requires Node 18+.

Log in

You'll need an API key: in the web app, go to Settings → MCP access → Generate key (the pls_… key is shown once — copy it).

pliris login                 # paste your pls_… key (or --api-key)
pliris whoami                # verify the key + list reachable bands

Key resolution order: --api-key flag → PLIRIS_API_KEY env → ~/.config/pliris/config.json (mode 600).

Commands

Command What it does
pliris login / logout / whoami Manage and verify your saved key
pliris bands List the bands you can access
pliris songs list --band <id> [--search <q>] [--limit n] [--offset n] List songs in a band
pliris arrangements list --song <id> List arrangements for a song
pliris setlists list --band <id> List setlists for a band
pliris setlist <setlist_id> Show a setlist with ordered items
pliris templates list List your custom Ableton templates (use an id as build --template <id>)
pliris ask "<question>" [--band <id>] Natural-language, AI-summarized answer
pliris build (--setlist <id> | --arrangement <id>) [--template <name>] [--name <set>] [--no-samples] [--wait] [--out file.zip] Build a downloadable Ableton set in the cloud
pliris build status <job_id> Check a build's progress / get its download link
pliris members list [--account <id>] [--band <id>] List members
pliris members invite --email <e> --account <id> --role <admin|member> [--access view|download|manage] [--band <id>… | --all-bands] Invite a member (prompts for anything omitted)
pliris members remove --email <e> --account <id> Remove a member
pliris tools List the MCP tools the server exposes
pliris skill [--out file.zip] Download the AI skill bundle

Global flags: --json (raw JSON for jq/scripts), --api-key <key>, --server <url> (advanced).

Examples

pliris bands
pliris songs list --band 1234-… --search "amazing grace"
pliris ask "what songs do we have in C minor around 120 bpm?"
pliris setlists list --band 1234-… --json | jq '.[].name'
pliris templates list --json | jq '.[] | {id, name}'

Building an Ableton set from the CLI:

pliris build --setlist <setlist_id> --wait                 # print the link
pliris build --arrangement <id> --template playback_intro --out song.zip
pliris build --arrangement <id> --template <custom-template-uuid>
pliris build status <job_id>

Pro tip: Everything the CLI can do, an AI assistant connected over MCP can do too — same tools, same permissions. If you'd rather ask in plain English than remember flags, see Connecting AI Assistants & the Pliris API.

Good to know

  • Acts as you. Every command runs through the same permission checks as the web app — you can only touch bands you can already access.
  • Subscription-gated. Commands require an active Bands subscription.
  • Rate limit: 60 requests/minute per API key, shared across every client using that key.

Frequently asked questions

Do I need to install the Pliris CLI before using it?

No — you can run it without installing via npx @fromstudiotostage/pliris --help, or install it globally with npm install -g @fromstudiotostage/pliris. Either way it requires Node 18+.

Where do I get an API key for the Pliris CLI?

In the web app, go to Settings → MCP access → Generate key. The pls_… key is shown only once — copy it, then run pliris login and paste it (or pass it via --api-key or the PLIRIS_API_KEY environment variable).

Can I use the Pliris CLI in scripts?

Yes — every command supports the global --json flag, which outputs raw JSON you can pipe to jq or use in automation, e.g. pliris setlists list --band <id> --json | jq '.[].name'.

Is there a rate limit on the Pliris CLI?

Yes — 60 requests per minute per API key, shared across every client (CLI, MCP, or otherwise) using that same key.

Can the Pliris CLI access bands I'm not a member of?

No — the CLI acts as you and runs every command through the same permission checks as the web app, so you can only touch bands you can already access. Commands also require an active Bands subscription.

Where to go next

Hit a snag, click the support bubble in the bottom-right corner of any page, or email support@fromstudiotostage.com. You'll hear back within 24 hours.