Yungle

Yungle for developers

Send large files from your terminal, your scripts and your AI assistant.

Private, sustainable file transfer: a WeTransfer alternative with a CLI, an MCP server, typed SDKs and webhooks.

Website · Docs · API reference · CLI · MCP · TypeScript · Python

npm install -g yungle-cli

yungle login # opens your browser, once yungle send ./render.mov # uploads resumably, prints the link

Want Yungle to email the link for you? Sign in with an API key (yungle login --key) and add --to client@example.com. A browser sign-in makes links but never emails anyone, so a phished sign-in code can't be used to mail strangers.

What's in here

| [CLI](apps/cli) | npm i -g yungle-cli brew install heindewilde/yungle/yungle | Send, receive and sync files from a terminal or CI — both ways, folders kept, checksums verified. Resumes after a dropped connection or a closed lid | | [MCP server](packages/mcp-server) | In Claude's directory https://yungle.co/mcp | Connect Claude, Cursor or any MCP client with one sign-in: ask what arrived, share big files (Yungle can fetch them from a URL), download what you were sent, approve every send | | [TypeScript SDK](packages/api-client) | npm i yungle-client | The whole API, typed and dependency-free, with resumable uploads from any Blob. Node, Bun, Deno, edge runtimes | | [Python SDK](python) | pip install yungle | The API from Python, with a one-call send() that handles the upload | | [GitHub Action](https://github.com/heindewilde/yungle-send-action) | uses: heindewilde/yungle-send-action@v1 | Send build artefacts to a client from CI and get the link back as an output | | [Examples](examples) | | GitHub Actions, nightly reports, and more at docs.yungle.co/guides/send-from-ci |

All of it talks to the same public REST API (OpenAPI 3.1), which CI checks these clients against on every change.

The CLI

Built to be pleasant for a person and predictable for a script. Pretty at a terminal, just the link when piped, JSON with --json.

yungle send ~/Shoot --to anna@studio.nl --message "Final selects"   # send a folder

yungle send dist/ --json | jq -r .url # in a script yungle get https://yungle.co/t/emerald-palm-a5mt # download, no account needed yungle send --from-url "https://bucket.s3.eu-central-1.amazonaws.com/render.mov?…" # Yungle fetches it yungle pull --collection 01J8Z3M9Q0W4 # your collection, to disk yungle status # who downloaded what yungle watch ~/Renders --collection 01J8Z3M9Q0W4 # upload new files as they land yungle webhooks listen --forward-to http://localhost:8080/hooks # test webhooks locally

• Resumable, big uploads. Interrupt yungle send, run it again, and it continues from the last committed part instead of starting over.
• Guided when you leave something out. yungle send on its own asks what to send and to whom. Never in CI, never with --json or --yes: a script can't hang on a question.
• Errors tell you the fix. Every failure ends with the one command that gets you unstuck, and a typo gets a *did you mean*.
• Tab completion for zsh, bash and fish: yungle completion zsh.

Full reference: apps/cli · docs.yungle.co/cli

Connect your AI assistant

In Claude: add Yungle from Claude's connector directory and sign in.

Anywhere else (Cursor, VS Code, any MCP client): add Yungle as a remote MCP server and sign in once. No key to copy.

https://yungle.co/mcp

Then ask things like *"Did Anna download the final set?"*, *"Which deliveries expire this week?"* *"Share these three files with the client."*, *"Send the client the render in our S3 bucket."* or *"What's in the link Anna sent me?"* A chat cannot carry a 40 GB file, so the assistant doesn't: Yungle fetches it from where it already is, or the assistant runs a one-file npx yungle-cli put command in its shell. The assistant prepares; you approve every send before an email leaves. There is no tool that deletes, revokes or invites, and everything the server returns is labelled as untrusted data, because a filename can carry a prompt injection.

Prefer a local server with an API key? yungle mcp install writes the config for Claude Desktop, Claude Code, Cursor or Windsurf. Details: packages/mcp-server.

The SDKs

import { YungleClient } from 'yungle-client';

const yungle = new YungleClient({ apiKey: process.env.YUNGLE_API_KEY! }); for await (const t of yungle.allTransfers()) console.log(t.title, t.downloadCount);

from yungle import Yungle

sent = Yungle().send(["render.mov"], to=["client@example.com"], message="Final cut") print(sent["url"])

Both retry what is safe to retry, put an Idempotency-Key on every POST so a retry never makes a second copy, follow cursor pagination for you, and verify webhook signatures.

Webhooks

Get told instead of polling: transfer.ready, transfer.downloaded, transfer.expiring, transfer.expired, and on paid plans collection.file_uploaded. Each delivery is signed with HMAC-SHA256 and retried with backoff. No public URL? Leave it out and pull the events instead.

import { verifyWebhook } from 'yungle-client';

const ok = await verifyWebhook(rawBody, req.headers['yungle-signature'], process.env.YUNGLE_WEBHOOK_SECRET!);

Plans and limits

Every account can use the API, the CLI and the MCP server, the free plan included: transfers up to 10 GB, contacts, webhooks, and downloading any link. Collections and files that never expire come with a paid plan. The first 10 GB of API uploads each month are free, then €0.02/GB from prepaid credit. Pricing

Why Yungle

• In Europe, run by a European company. Your files are stored and served from EU infrastructure.
• Always encrypted. Every file gets its own key, and transfers can be end-to-end encrypted in the browser when you need it.
• Sustainable. Renewable hydropower, in a data centre with a PUE of 1.13. What that does and doesn't mean.

Not reachable from here: your vault and end-to-end encrypted transfers. Their keys are derived in your browser and never sent to Yungle, so no API can read them. See what the API can't do.

Contributing

pnpm install

pnpm typecheck && pnpm lint && pnpm test && pnpm build pnpm contract # check the clients (operations and types) against the live OpenAPI spec

This repository is where the clients are developed; the Yungle service itself is not open source. Issues and pull requests are welcome, see CONTRIBUTING.md. Security reports go through security.txt.

MIT