Pricing
Pay per event
Search for LinkedIn profiles with filters and extract detailed profile information, including work experience, education history, location and more. No cookies or account required.
4.1 (5)
Pricing
Pay per event
78
1.2K
623
Issues response
7.4 hours
Last modified
3 days ago
You can access the LinkedIn Profile Search Scraper No Cookies ✅ Find all people 📧 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.
![LinkedIn People Profiles, Emails Extractor By URL [ No cookie ] avatar](https://images.apifyusercontent.com/4EDEjoZp3TJXR7HX1Ta3PCR94ncbhieMZesgMosF3XM/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vNGhJSXhTVmhGYW9abjhmSGcvd05KUkNUcmlRWUNPMEZ4RHQtSW4uanBn.webp){kind=avatar}
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?actors=harvestapi/linkedin-profile-search", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}You have a few options for interacting with the MCP server:
Use mcp.apify.com via mcp-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/?actors=harvestapi/linkedin-profile-search 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/?actors=harvestapi/linkedin-profile-search", "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.