
Linkedin Mutual Connections Parser
Pricing
$25.00/month + usage

Linkedin Mutual Connections Parser
Allows you to extract all informations from mutual connections of a linkedin profile url (1st and 2nd). Full name, jobtitle, premium status, followers, linkedin url, network distance, location, number of mutual connections. Does not need to be in your network to check for mutual connections
5.0 (1)
Pricing
$25.00/month + usage
14
Total users
241
Monthly users
29
Runs succeeded
97%
Issues response
0.32 hours
Last modified
2 months ago
You can access the Linkedin Mutual Connections Parser 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-mutual-connections-parser", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Linkedin Mutual Connections Parser
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-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-mutual-connections-parser
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-mutual-connections-parser", "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.