Linkedin Company Details Scraper & Finder (No Cookies) ✅ Bulk
Pricing
$4.00 / 1,000 companies
Linkedin Company Details Scraper & Finder (No Cookies) ✅ Bulk
Extract detailed information from LinkedIn Companies such as company name, address, phone numbers, website, employee count, and more. Find LinkedIn company URLs by name in Bulk. No cookies or account required.
5.0 (1)
Pricing
$4.00 / 1,000 companies
14
Total users
189
Monthly users
153
Runs succeeded
>99%
Last modified
16 days ago
You can access the Linkedin Company Details Scraper & Finder (No Cookies) ✅ Bulk 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=harvestapi/linkedin-company", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Linkedin Company Details Scraper & Finder (No Cookies) ✅ Bulk
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=harvestapi/linkedin-companyalong 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=harvestapi/linkedin-company", "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.
