What is co.yungle/yungle?

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

How do I install co.yungle/yungle?

Clone co.yungle/yungle from https://github.com/heindewilde/yungle-clients and configure it as an MCP server in your client (Claude Desktop, Cursor, or VS Code).

Is co.yungle/yungle open source?

Yes, co.yungle/yungle is open source under the MIT license. Source code is available at https://github.com/heindewilde/yungle-clients.

What category does co.yungle/yungle belong to?

co.yungle/yungle is listed under File Systems MCP servers on MCPFind.

co.yungle/yungle — MCP Server for File Systems

Yungle clients

Client libraries for Yungle — a private, EU-hosted file transfer service, and an alternative to WeTransfer for people whose files need to stay in Europe.

Package
`yungle-cli`	`npm i -g yungle-cli`	Send and sync files from your terminal, resumably
`yungle-mcp`	`npx -y yungle-mcp`	Read your transfers from an AI assistant (MCP)
`yungle-client`	`npm i yungle-client`	Typed SDK for the API

Reading is free on any Yungle account. Creating, sending and uploading come with a paid plan. Get a key from Settings → API keys.

API reference: https://yungle.co/developers
OpenAPI 3.1 spec: https://yungle.co/api/v1/openapi.json

Why a CLI

Yungle's upload engine is resumable at part granularity and sized for 100 GB transfers. A browser tab has to stay open for the whole upload, and a closed laptop lid costs you the file. yungle send does not: interrupt it, run the same command again, and it continues from the last committed part.

What these cannot do

Your vault and end-to-end encrypted transfers are not reachable, and cannot be — their keys are derived in the client and never sent to Yungle. The MCP server additionally has no tool that sends, deletes, invites or revokes; it reads metadata only, by design. See https://yungle.co/developers/unsupported.

Development

pnpm install
pnpm -r test
pnpm -r build

The Yungle server itself is not open source; this repository holds only the clients. Issues and pull requests about the clients are welcome here.

MIT

Set up in your AI client

AI clientOperating system

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json

{
  "mcpServers": {
    "co-yungle-yungle": {
      "command": "npx",
      "args": [
        "-y",
        "yungle-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Compatible MCP Clients

co.yungle/yungle works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.

Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.

VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.

Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.

Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

co.yungle/yungle