Install and sign in
npm install -g yungle-cli
yungle auth login # paste a key from Settings → API keys
yungle auth statusThe key is read from YUNGLE_API_KEYfirst, then from the CLI’s config file. On a build server, set the environment variable and skip auth login entirely.
Commands
yungle auth login
Asks for a key and checks it against the API before saving it, so a typo fails now rather than on your next upload. The key is stored in the CLI’s config file; YUNGLE_API_KEY in the environment takes precedence over it, which is what you want on a build server.
yungle auth status
Prints the workspace and plan the current key belongs to, or says you are not signed in.
yungle send <paths…>
Creates a transfer from files and folders (folders keep their structure), uploads them resumably, sends it, and prints the link. With no --to it is a link-only transfer and nobody is emailed. If the upload is interrupted, run the same command again and it continues where it stopped.
| Flag | What it does |
|---|---|
--to <email> | recipient (repeatable, or comma-separated) |
--message <text> | note for the recipients |
--title <text> | label for your dashboard |
--password <text> | recipients must enter this |
--expires <days> | lifetime, clamped to your plan |
yungle push <paths…> --collection <id>
Uploads files and folders into an existing collection, building its folder tree from the paths you give. Collections are a paid feature. Resumable in the same way as send.
| Flag | What it does |
|---|---|
--folder <id> | target folder |
yungle ls transfers|collections|contacts
One line per item: id, name, size and — for transfers — download count and link.
yungle rm transfer <id>
Immediate and irreversible: the files’ encryption keys are destroyed, and links already sent stop working.
yungle mcp install
Adds the Yungle MCP server to an assistant’s configuration, with your key. It refuses a key that can write, so the assistant can read your transfers and collections but never send, delete or invite.
| Flag | What it does |
|---|---|
--client <id> | claude-desktop | claude-code | cursor | windsurf |
--dry-run | show what would change, write nothing |
yungle mcp status
Lists which assistants on this machine have the Yungle MCP server configured.
Global flags
| Flag | What it does |
|---|---|
--json | machine-readable output |
--url <base> | override the API base URL |
Scripting it
With --json, the result is one JSON object on stdout. Progress and diagnostics go to stderr, so a pipe into jq stays clean:
URL=$(yungle send ./render.mp4 --json | jq -r .url)
echo "Ready: $URL"send --json prints id, url, expiresAt and notified (the addresses that were emailed). push --json prints the collection id, the number uploaded and the collection’s url.