π₯ LinkedIn Jobs Scraper β Multiple Titles & Locations in One!
Pricing
$1.00 / 1,000 results
π₯ LinkedIn Jobs Scraper β Multiple Titles & Locations in One!
This LinkedIn Job Scraper allows you to extract job listings across multiple job titles and locations: π Key Features: Input multiple job titles (e.g. "Software Engineer", "Data Analyst") Input multiple locations (e.g. "London", "New York", "Berlin") Filters by work type: On-site, Remote, Hybrid
5.0 (3)
Pricing
$1.00 / 1,000 results
4
Total users
33
Monthly users
23
Runs succeeded
>99%
Issues response
32 days
Last modified
a month ago
You can access the π₯ LinkedIn Jobs Scraper β Multiple Titles & Locations in One! 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": { "local-actors-mcp-server": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--actors", "lntb/linkedin-jobs-scraper---multiple-titles-locations-in-one" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}Configure MCP server with π₯ LinkedIn Jobs Scraper β Multiple Titles & Locations in One!
You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:
{ "mcpServers": { "remote-actors-mcp-server": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=lntb/linkedin-jobs-scraper---multiple-titles-locations-in-one", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported 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.
