LinkedIn Jobs Scraper · No Login · $0.5/1k
Pricing
from $0.35 / 1,000 jobs
LinkedIn jobs scraper: search public job postings by keyword, location, date, company or LinkedIn URL and export them to Excel, CSV or JSON, no login. Title, company, location, salary, applicants, full description, seniority, job function, industries, poster. $0.50 per 1,000 jobs, no start fee.
You can access the LinkedIn Jobs Scraper · No Login · $0.5/1k 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 Search Jobs Scraper [Bypass 1K limit][Without Cookies] avatar](https://images.apifyusercontent.com/R2Hg7HUu4OYUkhlVwW1-lPBPl1NGLT-ic5bF4_S0Hnk/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vMGlpckJJNUNkSTFIbkJxVnQvS0ZxbEVUOFFKSm1xbk8xUjgtbGlua2VkaW4ucG5n.webp){kind=avatar}
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,alfalfa/linkedin-jobs-scraper" } }}The configuration above connects to the hosted Apify MCP server with the LinkedIn Jobs Scraper & API - No Login Needed 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 & API - No Login Needed Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,alfalfa/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.