Linkedin data scraper ( EVERY-THING )
Pricing
$125.00/month + usage
Linkedin data scraper ( EVERY-THING )
This actor can scrape anything from linkedin. Anything includes Person Data, Company Data, Person Posts, Company Posts, Search Jobs, Search People, Search Companies, Search Posts and much more. Cannot afford pricing? Contact us, we'll discuss a better pricing.
5.0 (1)
Pricing
$125.00/month + usage
47
Total users
1.2K
Monthly users
180
Runs succeeded
>99%
Issues response
8.3 hours
Last modified
2 months ago
You can access the Linkedin data scraper ( EVERY-THING ) 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=muhammad_usama/linkedin-data-scraper-every-thing", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Linkedin data scraper ( EVERY-THING )
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom 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=muhammad_usama/linkedin-data-scraper-every-thingalong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=muhammad_usama/linkedin-data-scraper-every-thing", "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.
