Youtube Comments Scraper (Pay Per Result)
Pricing
$0.50 / 1,000 comments
Youtube Comments Scraper (Pay Per Result)
YouTube Comments Scraper, the ultimate solution for extensive YouTube comments data retrieval. With its high-speed scraping abilities, it provides unmatched effectiveness and thoroughness. Additionally, its cost-effectiveness is unmatched, priced at just $0.50 per 1000 comments!
5.0 (1)
Pricing
$0.50 / 1,000 comments
24
Total users
568
Monthly users
65
Runs succeeded
96%
Issues response
7 hours
Last modified
9 hours ago
You can access the Youtube Comments Scraper (Pay Per Result) 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=apidojo/youtube-comments-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Youtube Comments Scraper (Pay Per Result)
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom 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=apidojo/youtube-comments-scraperalong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=apidojo/youtube-comments-scraper", "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.
