Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Yungle

by heindewildeversion 0.3.2i★ –iComputer or cloud
Registry nameco.yungle/yungle

Install

Overview

Description from the maker (original English)

Ask about your Yungle transfers, share big files, download what you're sent. Approve every send.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: YUNGLE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: YUNGLE_API_KEY, YUNGLE_API_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://yungle.co/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "yungle": {
      "command": "npx",
      "args": [
        "-y",
        "yungle-mcp"
      ],
      "env": {
        "YUNGLE_API_KEY": "your-value",
        "YUNGLE_API_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http yungle https://yungle.co/mcp

Or run it on your computer

claude mcp add yungle --env YUNGLE_API_KEY=your-value --env YUNGLE_API_URL=your-value -- npx -y yungle-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yungle": {
      "url": "https://yungle.co/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yungle": {
      "command": "npx",
      "args": [
        "-y",
        "yungle-mcp"
      ],
      "env": {
        "YUNGLE_API_KEY": "your-value",
        "YUNGLE_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "yungle": {
      "type": "http",
      "url": "https://yungle.co/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "yungle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yungle-mcp"
      ],
      "env": {
        "YUNGLE_API_KEY": "your-value",
        "YUNGLE_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://yungle.co/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • YUNGLE_API_KEY secret required env
    A Yungle API key from https://yungle.co/dashboard/settings/api. Read scopes to answer questions; add transfers:write to share links. Or skip keys: connect to https://yungle.co/mcp and sign in.
  • YUNGLE_API_URL env
    Override the API base URL. Only useful for development against a local Yungle instance; leave unset to use https://yungle.co/api/v1.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain yungle.co (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32466 servers in this category
  • Published to the registry more recently than 60% of the other 32466 servers in this category
  • Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Yungle safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: YUNGLE_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

InstallWhat it's for

| [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

Ask PopNx