
Linkedin Posts Reactions Scraper
Pricing
$25.00/month + usage

Linkedin Posts Reactions Scraper
Extract people who comments, mentions and likes from linkedin post or article. Allows you to extract all interactions / reactions from a url. Input can be a /posts url or article url. Also provide a /company or /in url and it will parse multiple posts from the source (organic and promoted LinkedIn)
0.0 (0)
Pricing
$25.00/month + usage
14
Total users
286
Monthly users
19
Runs succeeded
85%
Issues response
2.7 hours
Last modified
16 days ago
You can access the Linkedin Posts Reactions Scraper 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=saswave/linkedin-posts-interactions-parser", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Linkedin Posts Reactions Scraper
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=saswave/linkedin-posts-interactions-parser
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=saswave/linkedin-posts-interactions-parser", "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.