Why this server?
Enables real-time web research capabilities, allowing users to search Google and extract webpage content, which can be used to find LinkedIn profiles.
Why this server?
Similar to the above, this server also provides web research capabilities using Google search and webpage content extraction, facilitating the discovery of LinkedIn profiles.
Why this server?
Again, this server enables web research, which is helpful in finding LinkedIn profiles by name.
Why this server?
Enables advanced search and content extraction using the Tavily API, useful for finding specific information such as LinkedIn profiles.
Why this server?
Extracts and transforms webpage content into clean, LLM-optimized Markdown. Can be used in conjunction with a search to retrieve and format LinkedIn profile information.
Why this server?
Enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API. This can be used to search for LinkedIn profiles.
Why this server?
Provides integration between Hunter API and LLM providers supporting the MCP protocol, allowing natural language interaction with Hunter B2B data for finding and managing company and people information, including email addresses associated with LinkedIn profiles.
Why this server?
Integrates Atlassian products (Confluence, Jira) with Model Context Protocol, enabling easy access to Confluence content and Jira tickets through the MCP interface. While not directly linkedin related, Atlassian products may mention linkedIn profiles.
Why this server?
A Model Context Protocol server providing comprehensive access to LinkedIn data and functionality, enabling data retrieval and user account management through the HorizonDataWave API.