
LinkedIn Jobs Scraper | Remove Duplicate Jobs
Pricing
from $0.65 / 1,000 results

LinkedIn Jobs Scraper | Remove Duplicate Jobs
LinkedIn Jobs Scraper | Remove Duplicate Jobs. The LinkedIn jobs scraper allows you to collect jobs in 2 ways: By providing one or more start URLs, or By entering multiple keywords, search queries. You can use either method individually or combine both.
3.2 (4)
Pricing
from $0.65 / 1,000 results
24
Total users
396
Monthly users
216
Runs succeeded
98%
Issues response
5.3 hours
Last modified
3 days ago
You can access the LinkedIn Jobs Scraper | Remove Duplicate Jobs 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=cheap_scraper/linkedin-job-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with LinkedIn Jobs Scraper | Remove Duplicate Jobs
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=cheap_scraper/linkedin-job-scraper
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=cheap_scraper/linkedin-job-scraper", "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.