For AI agents

Let your agent deliver files — within limits you set.

Agents produce reports, exports and renders that a person needs. Yungle gives them a way to hand those over, and an MCP server that can only read.

MMeet Mateo, aI engineerBarcelona · builds assistants for a design agency · an illustrative example

AI engineer

A week with Mateo.

Monday
One command to connect.
Mateo runs yungle mcp install and the assistant can read transfers, collections and contacts. It refuses a key that can write.
API, CLI & MCP
Tuesday
“Did the client download it?” answered in a sentence.
The assistant looks up who has downloaded last week’s delivery, instead of Mateo opening the dashboard.
Transfers
Thursday
The agent prepares; a person sends.
The assistant can draft a transfer, and says plainly that nothing was sent and nobody was emailed. Sending stays a human decision.
API, CLI & MCP
Always
Some files stay out of reach.
The vault is not reachable through the API or the MCP server, by design: its key never leaves the owner’s browser.
Vault

The MCP server cannot send anything. That is deliberate, not a missing feature.
There are no webhooks yet; poll for download receipts.
The vault and end-to-end encrypted transfers are out of reach of agents, because their keys never leave a browser.

How do I run the MCP server?

With npx -y yungle-mcp and an API key. The developer guide walks through the setup.

Why can’t the MCP server send files?

Because a model can be talked into things. A read-only server means a confused or manipulated agent cannot share your files with anyone.

Is it free?

The MCP server and API access to transfers are available without paying.

10 GB, free, right now — no account, no card, no ads. Pay us only when you want your work to stay put.