Yungle MCP server
{
"mcpServers": {
"yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp@latest"
]
}
}
}{
"mcpServers": {
"yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp@latest"
]
}
}
}{
"mcpServers": {
"yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp@latest"
]
}
}
}{
"servers": {
"yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp@latest"
]
}
}
}{
"mcpServers": {
"yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y yungle-mcpversion 0.1.2
What it does
MCP server that provides read-only access to Yungle file transfer metadata. Lets you query information about file deliveries, who downloaded them, and expiration details through an AI assistant. For users of Yungle, a private EU-hosted file transfer service.
- Check the status and download history of file transfers you've sent through Yungle
- Retrieve metadata about expired or active transfers and their recipients
- Query delivery information about files without leaving your AI assistant interface
Tools this server exposes
| Tool | Does |
|---|---|
| read_transfers | Query metadata about your Yungle file transfers, including delivery status, downloads, and expiration information |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.