LinkedIn MCP Server
Related Servers
Alternatives to LinkedIn MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to access LinkedIn data through the user's logged-in browser session, supporting profiles, companies, job searches, messaging, and feed/posts.21Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to use an existing browser session to read profiles and companies, search jobs and people, and manage messages and connection requests on LinkedIn.21Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to access LinkedIn through the user's own browser session to read profiles, research companies, find jobs, and manage conversations and connection requests.25Apache 2.0
- AlicenseAqualityBmaintenanceGives AI agents access to LinkedIn through your own browser session, enabling profile and company research, job searching, and management of conversations and connection requests.25Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with LinkedIn by scraping profiles, companies, job postings, and getting personalized job recommendations using authenticated browser automation.1711,806 PyPI4,230Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to browse profiles and companies, manage messages and inboxes, and search jobs, posts, and people through a locally logged-in browser session. All actions run on the user's own machine.19Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a distinct resource/action: people, companies, jobs, messaging, feed, and session management. Overlapping tools like get_feed/search_posts/get_company_posts and get_company_employees/search_people are explicitly differentiated in their descriptions, so an agent should not misselect.
All tool names follow a verb_noun snake_case pattern, primarily get_* and search_*, with a few clear action verbs like send_message, connect_with_person, and close_session. The naming is predictable and consistent across the full set.
At 19 tools, the server is in the 16-25 range that feels heavy, even though the LinkedIn domain is broad. Some niche helpers like get_sidebar_profiles and close_session could be considered non-essential, but the count is not extreme enough to be chaotic.
Core workflows are covered end-to-end: search people, companies, and jobs; retrieve details; connect; message; and read feeds/inbox. Obvious gaps are modest, such as no ability to post content, manage connections, or apply to jobs, but these are not central to the apparent sales/recruiting use case.