LinkedIn Profile Scraper MCP Server
Related Servers
Alternatives to LinkedIn Profile Scraper MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for LinkedIn API integration. Enables authentication, profile access, connections, search, messaging, and feed management via OAuth2.-
- FlicenseAqualityDmaintenanceMCP server that enables LinkedIn profile scraping and search using Selenium-based scraper with support for multiple LinkedIn accounts.2-
- AlicenseAqualityCmaintenanceREST API and MCP server for AI agents to extract structured LinkedIn profile data.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that lets you analyze your own LinkedIn profile with a local LLM (LM Studio). It uses Playwright to reuse your browser session, fetch profile data as JSON, and provides tools for session management and profile analysis.1MIT
- FlicenseNot gradedqualityDmaintenanceA Node.js-based Model Context Protocol server that exposes Proxycurl's LinkedIn data API, allowing MCP-compatible clients to access LinkedIn profile data, company information, and search for employees.-
- AlicenseAqualityBmaintenanceAn MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.19Apache 2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (get_profile), and with only one tool, consistency is inherently perfect as there are no other tools to compare against.
A single tool is too few for a server labeled as a 'LinkedIn Profile Scraper MCP Server,' which suggests a broader scope. This minimal set feels thin and underdeveloped for scraping tasks that might include multiple operations like search, batch processing, or data extraction beyond single profiles.
The tool surface is severely incomplete for a LinkedIn scraper. It only allows fetching a single profile by URL, missing essential operations such as searching for profiles, handling authentication, pagination, or extracting additional data like connections or posts, which are typical in scraping workflows.