What the yungle MCP server does
The yungle MCP server gives an AI assistant access to information and actions around Yungle file deliveries. It is suited to questions such as whether a recipient downloaded a delivery, which files arrived, and which transfers are close to expiration.
The server also supports file handling. An assistant can download files that were sent to the account, share large files with a client, and ask Yungle to fetch a file from an existing URL before sharing it. These operations are useful when the file already exists in object storage or another reachable location and does not need to pass through the chat interface.
Status lookups are read-only from the user’s perspective. Sending a file is an action that requires explicit approval before the send occurs. The repository states that the server does not provide tools for deleting, revoking, or inviting.
How the yungle MCP server works
The hosted service is exposed as a remote MCP endpoint at https://yungle.co/mcp. Add that endpoint to an MCP client and complete the Yungle sign-in flow once. The README identifies Claude, Cursor, VS Code, and other MCP clients as supported for the remote connection.
For local use, the repository provides yungle mcp install, which writes configuration for Claude Desktop, Claude Code, Cursor, or Windsurf. The README also describes API-key authentication for local-server use, although it does not specify a required MCP server environment variable in the available material.
The assistant does not upload a large file through the conversation itself. For a URL-based send, Yungle fetches the source file. Alternatively, the assistant can run a one-file npx yungle-cli put command in its shell. Returned data is labelled as untrusted, including filenames, because file metadata can contain prompt-injection content.
Tools and capabilities
The yungle MCP server supports these documented workflows:
- Inspect deliveries and received files.
- Check who downloaded a file and when.
- Find transfers that are expiring.
- Download files sent to the authenticated account.
- Share files with a client after approval.
- Send a file that Yungle retrieves from a URL.
The service supports accounts on the free plan. The README states that free accounts can use the API, CLI, and MCP server, with transfers up to 10 GB. Collections and files that never expire require a paid plan.
Limitations and notes
The yungle MCP server cannot access a Yungle vault or end-to-end encrypted transfers because their keys are derived in the browser and are not sent to Yungle. It also has no documented delete, revoke, or invitation tool.
A chat client is not a suitable transport for very large files. The documented workflow is for the server or CLI to retrieve or transfer the file separately. Sending is approval-gated, so an assistant can prepare a delivery without silently emailing a link to a recipient.
The service stores and serves files from EU infrastructure, and the README states that files are encrypted. Those service properties do not expand the MCP server’s access to browser-held vault keys or encrypted transfers.