Facebook Comments PPR avatar
Facebook Comments PPR

Pricing

$0.50 / 1,000 comments

Go to Store
Facebook Comments PPR

Facebook Comments PPR

Developed by

Jan Danecki

Jan Danecki

Maintained by Community

Scrap Facebook comments fast and easy. It is designed to be fast and efficient, so it can extract a large number of comments for low price. It is also less likely to be blocked by Facebook.

1.0 (2)

Pricing

$0.50 / 1,000 comments

8

Total users

305

Monthly users

56

Runs succeeded

>99%

Issues response

4.1 days

Last modified

4 months ago

You can access the Facebook Comments PPR 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=danek/facebook-comments-ppr",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Facebook Comments PPR

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=danek/facebook-comments-ppr 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=danek/facebook-comments-ppr",
"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.