1. A key that can only read
In Settings → API keys, create a key with only the :read scopes — transfers:read, collections:read, contacts:read. The installer refuses anything that can write, because this key is about to sit in a config file on your machine.
2. Connect your assistant
npm install -g yungle-cli
yungle auth login # paste the read-only key
yungle mcp install --client claude-desktop --dry-run # see the change
yungle mcp install --client claude-desktop
yungle mcp status--client also takes claude-code, cursor and windsurf. Restart the assistant so it picks up the new server.
3. Ask it things
| You ask | It uses |
|---|---|
| “Has De Vries downloaded the Q3 report yet?” | list_transfers, get_transfer_downloads |
| “What is still sitting in the Harbour collection?” | list_collections, list_collection_files |
| “Who have I invited to the wedding gallery?” | list_guests |
| “How much storage do I have left?” | get_account |
| “What is Anna’s email address?” | list_contacts |
Download receipts count one visit as one download, even when the recipient saved eight files. The tool’s description tells the model to count distinct sessions, so “how many times” comes back right.
4. Where it hands back to you
- Sending. The server has no tool that uploads or emails anything — file bytes never travel through an MCP connection. When you ask it to send, it should tell you to run
yungle sendor use the browser. (The one tool that writes,create_transfer, only makes a draft, and needs a write scope the installer will not accept.) - Deleting, revoking, inviting. No tool exists for any of them, so a misread instruction cannot take a link away from a client.
- Contents. The assistant sees names, sizes and receipts, never what is inside a file. The vault is not visible at all.
Filenames and messages come from other people. The server labels them as untrusted data, so a file called “ignore previous instructions” is reported, not obeyed.
Every tool, with its inputs, is in the MCP reference.