MCP server

The Yungle MCP server lets an AI assistant answer questions about your files — what did I send, has the client downloaded it, what is in this collection — using the Model Context Protocol. It reads. It does not send, delete, invite or revoke anything.

Install

The quickest way is the CLI, which writes the configuration for you:

npm install -g yungle-cli
yungle auth login
yungle mcp install --client claude-desktop   # or: claude-code, cursor, windsurf
yungle mcp status

mcp install refuses a key that can write. Create a separate key with only the :read scopes for your assistant — a key sitting in a config file should be worth as little as possible to whoever finds it. Add --dry-run to see the change first.

Or add it by hand, to any MCP client that runs stdio servers:

{
  "mcpServers": {
    "yungle": {
      "command": "npx",
      "args": ["-y", "yungle-mcp"],
      "env": { "YUNGLE_API_KEY": "yk_live_…" }
    }
  }
}

Supported by mcp install: Claude Desktop, Claude Code, Cursor, Windsurf.

Tools

ToolWhat it answersInputs
get_accountHow much storage is used and left, which plan, and what this key may do.—
list_transfersRecent transfers with size, recipients, download count, expiry date and share link.—
get_transferThe files in a transfer with their malware-scan verdicts, and per-recipient status.id
get_transfer_downloadsDownload events with timestamps. One visit is one download: count distinct sessionIds.id
list_collectionsCollections with file counts, sizes and when each was last touched. Never the vault.—
get_collectionOne collection with its secret share link, file count, total size and expiry.id
list_collection_filesFilenames, sizes and types — never file contents.id, folderId (optional)
list_foldersThe folder tree, each folder with its full path. Build the tree from parentId.id
list_guestsWho is invited and whether they accepted.id
list_contactsThe workspace address book. A contact grants no access by itself.—
create_transferCreates a draft and returns its id. Uploads nothing and emails nobody — you finish it in the browser or with yungle send.files, title (optional), expiresInDays (optional)

What it cannot do

  • Send. create_transfer prepares a draft and returns its id. It uploads nothing and emails nobody — file bytes never travel through an MCP connection. You finish the send in the browser, or with yungle send. It also needs transfers:write, which mcp install refuses — so with a server set up that way, the assistant can only read.
  • Delete, revoke or invite. No tool does any of these, so an assistant that misreads an instruction cannot take a link away from a client.
  • Read file contents. It sees names, sizes, types and receipts — never what is inside a file.
  • Open your vault. The vault is never listed, and its key is derived in your browser, so no server can read it.
Filenames, titles and messages come from people outside your control. The server marks them as untrusted data for the model, so a filename that reads like an instruction is treated as text, not obeyed.

See also