Linkedin Mass Company Profile Finder avatar
Linkedin Mass Company Profile Finder

Pricing

$20.00/month + usage

Go to Store
Linkedin Mass Company Profile Finder

Linkedin Mass Company Profile Finder

Developed by

SASWAVE

SASWAVE

Maintained by Community

Find company profile linkedin at scale with website domain. For strict and better matching, use quotes around the concerned characters

5.0 (1)

Pricing

$20.00/month + usage

4

Total users

65

Monthly users

14

Runs succeeded

>99%

Last modified

5 months ago

You can access the Linkedin Mass Company Profile Finder 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-mass-company-profile-finder",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Linkedin Mass Company Profile Finder

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/sse?actors=saswave/linkedin-mass-company-profile-finder 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/sse?actors=saswave/linkedin-mass-company-profile-finder",
"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.