pliris CLI

Command-line access to your From Studio to Stage catalogue (Pliris), over the same MCP server that powers the Claude/Cursor integrations. Every command maps to an MCP tool and runs with the exact permissions of your account — the CLI can't see or change anything you can't already in the web app.

Install

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

Requires Node 18+.

Authenticate

1. In the web app, go to Settings → MCP access and generate an API key (bnd_…). The key is shown once.
2. Save it to the CLI:

pliris login            # paste the key when prompted
pliris login --api-key bnd_xxx   # non-interactive

The key is stored in ~/.config/pliris/config.json (mode 600). You can also pass it per-invocation with --api-key, or set PLIRIS_API_KEY in your env.

Commands

| Command | Description | | --- | --- | | 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 ask "<question>" [--band <id>] | Natural-language question, AI-summarised | | pliris members list [--account <id>] [--band <id>] | List members | | pliris members invite --email <e> --account <id> --role <r> [--band <id>…] | Invite a member | | pliris members remove --email <e> --account <id> | Remove a member | | pliris build (--setlist <id> \| --arrangement <id>) [--template <name>] [--name <set>] [--no-samples] [--wait] [--out file.zip] | Build a downloadable Ableton Live set from a setlist or single arrangement | | pliris build status <job_id> | Check a set build's progress / get its download link | | pliris tools | List the MCP tools the server exposes | | pliris skill [--out file.zip] | Download the AI skill bundle |

Global flags

• --json — emit raw JSON (pipe into jq, scripts, etc.)
• --api-key <key> — override the saved/env key
• --server <url> — point at a different MCP server (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 members invite --email [email protected] --account abcd-… --role band_viewer --band 1234-…

Notes

• Rate limit: 60 requests/min per key (shared with other MCP clients on that key).
• Mutating commands (members invite / remove) respect your role — a viewer key will get a clear permission error.
• This package is a thin client; all logic lives server-side in the deployed MCP edge function.