Linkedin Company Employees Scraper | No Cookies
Pricing
$10.00 / 1,000 results
Linkedin Company Employees Scraper | No Cookies
Extract LinkedIn company employees without sharing your cookies or account. Get structured data including profile details, job titles, and current positions. No login required.
5.0 (3)
Pricing
$10.00 / 1,000 results
14
Total users
272
Monthly users
172
Runs succeeded
>99%
Issues response
1.1 days
Last modified
2 days ago
You can access the Linkedin Company Employees Scraper | No Cookies 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=apimaestro/linkedin-company-employees-scraper-no-cookies", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with LinkedIn Company Employees Scraper – No Login Required
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=apimaestro/linkedin-company-employees-scraper-no-cookiesalong 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=apimaestro/linkedin-company-employees-scraper-no-cookies", "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.
