
Linkedin Posts Search Scraper | No Cookies
Pricing
$5.00 / 1,000 results

Linkedin Posts Search Scraper | No Cookies
Scrape LinkedIn posts by keyword without login. Get post content, reactions, author details, and media. Sort by relevance or date. Perfect for research, analysis, and monitoring trends.
3.9 (7)
Pricing
$5.00 / 1,000 results
30
Total users
527
Monthly users
391
Runs succeeded
>99%
Issues response
13 hours
Last modified
6 days ago
You can access the Linkedin Posts Search Scraper | No Cookies 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=apimaestro/linkedin-posts-search-scraper-no-cookies", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with LinkedIn Posts Search Scraper – No Login Required
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=apimaestro/linkedin-posts-search-scraper-no-cookies
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=apimaestro/linkedin-posts-search-scraper-no-cookies", "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.