Linkedin Company Insights Scraper
Pricing
$30.00/month + usage
Linkedin Company Insights Scraper
Linkedin company insights scraper. Extract data for analysis and buy intents. Scrap data about: Employee count with history and median tenure, Employee distribution and headcount growth by function, Profile New hires, Profile Notable company alumni with exit date and new role, Total job openings
0.0 (0)
Pricing
$30.00/month + usage
4
Total users
58
Monthly users
21
Runs succeeded
82%
Issues response
20 hours
Last modified
a month ago
You can access the Linkedin Company Insights Scraper 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=saswave/linkedin-company-insights-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Linkedin Company Insights Scraper
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=saswave/linkedin-company-insights-scraperalong 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=saswave/linkedin-company-insights-scraper", "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.
