LinkedIn Company URL - Mass Finder avatar
LinkedIn Company URL - Mass Finder

Pricing

$10.00/month + usage

Go to Store
LinkedIn Company URL - Mass Finder

LinkedIn Company URL - Mass Finder

Developed by

ScrapeVerse

ScrapeVerse

Maintained by Community

Stop wasting time manually searching for LinkedIn company pages. With LinkedIn Mass Company URL Finder, input your company list and get instant access to their LinkedIn URLs. Automate your search and streamline your workflow today!

0.0 (0)

Pricing

$10.00/month + usage

6

Total users

155

Monthly users

33

Runs succeeded

>99%

Issues response

1.6 hours

Last modified

8 months ago

You can access the LinkedIn Company URL - Mass 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": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"sanjeta/linkedin-company-url---mass-finder"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with LinkedIn Company URL - Mass Finder

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=sanjeta/linkedin-company-url---mass-finder",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported 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.