LinkedIn Jobs Scraper
Pricing
Pay per usage
Scrape public LinkedIn job postings — title, company, location, salary, description and applicant count. No login, no cookies, no proxies.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
BERCIK Group
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
You can access the LinkedIn Jobs 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 API & Integrations in Apify Console.
![LinkedIn Jobs Scraper 💼 [No Cookies] — $1/1K 💰 avatar](https://images.apifyusercontent.com/hSIqPSmfrcrG6FFIoXaXxjcAINu_DmT7IPkN8_z73M4/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vcnBUYTM3bzFjdGZkRldaazktYWN0b3ItZWo0STRGQVpiTktrbUY3SjItVUlaa05peFE0MS1sb2dvLnBuZw.webp){kind=avatar}
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,bercikgroup/linkedin-jobs-scraper" } }}The configuration above connects to the hosted Apify MCP server with the LinkedIn Jobs Scraper — Export Job Postings (No Login) Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the LinkedIn Jobs Scraper — Export Job Postings (No Login) Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,bercikgroup/linkedin-jobs-scraper.
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.