YouTube Downloader avatar
YouTube Downloader

Deprecated

Pricing

$10.00/month + usage

Go to Store
YouTube Downloader

YouTube Downloader

Deprecated

Developed by

ApiLabs

ApiLabs

Maintained by Community

All-in-One YouTube Downloader: Easily integrate our affordable solution into your application to download high-quality videos, audio, and music from YouTube. Enjoy customizable formats and quality options, all at a cheaper price compared to other tools.

0.0 (0)

Pricing

$10.00/month + usage

4

Total users

30

Monthly users

1

Last modified

2 months ago

You can access the YouTube 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=apilabs/youtube-downloader",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with YouTube Downloader

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=apilabs/youtube-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=apilabs/youtube-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.