
Youtube Comments Scraper (Pay Per Results)
Pricing
$1.80 / 1,000 comments

Youtube Comments Scraper (Pay Per Results)
Easily collect full text YouTube comments with this tool! Just enter video URLs, and get all the data you need in JSON format, including comment text, like counts, and commenter info. Great for researchers and developers.
0.0 (0)
Pricing
$1.80 / 1,000 comments
1
Total users
19
Monthly users
3
Runs succeeded
>99%
Last modified
10 months ago
You can access the Youtube Comments Scraper (Pay Per Results) 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=easy_peasy_api/youtube-comments-scraper-pay-per-results", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Youtube Comments Scraper (Pay Per Results)
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-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=easy_peasy_api/youtube-comments-scraper-pay-per-results
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=easy_peasy_api/youtube-comments-scraper-pay-per-results", "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.