
Facebook Comments Scraper : Webhook Support
Pricing
Pay per event

Facebook Comments Scraper : Webhook Support
Effortlessly extract meaningful conversations from public Facebook posts. Designed for teams that need automated, reliable comment data at scale—just schedule the task, let the actor crawl, and receive results directly via your API. Ideal for sentiment analysis, research, and trend monitoring
5.0 (2)
Pricing
Pay per event
3
3
3
Last modified
4 days ago
You can access the Facebook Comments Scraper : Webhook Support 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/?actors=devninja/facebook-comments-scraper-webhook-support", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Facebook Comments Scraper : Webhook Support
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/?actors=devninja/facebook-comments-scraper-webhook-support
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/?actors=devninja/facebook-comments-scraper-webhook-support", "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.