Unlimited Torrent Downloader avatar
Unlimited Torrent Downloader

Pricing

$10.00/month + usage

Go to Store
Unlimited Torrent Downloader

Unlimited Torrent Downloader

Developed by

epctex

epctex

Maintained by Community

Seamlessly download and seed unlimited files from any Torrent website with no restrictions. Access Magnet, HTTP, and HTTPS files without any blocks and effortlessly seed the files for optimal performance.

1.0 (2)

Pricing

$10.00/month + usage

4

Total users

278

Monthly users

17

Runs succeeded

88%

Last modified

10 hours ago

You can access the Unlimited Torrent Downloader programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=epctex/torrent-downloader",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Torrent Downloader Wizard

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=epctex/torrent-downloader along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=epctex/torrent-downloader",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.