mcp-server-linkedin
Related Servers
Alternatives to mcp-server-linkedin
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityBmaintenanceEnables AI agents to access LinkedIn through the user's own browser session, so they can read profiles and company pages, search for jobs and people, and manage messages, conversations, and connection requests. Supports checking session status, reading the home feed and posts, and inspecting Easy Apply forms without submitting them.26Apache 2.0
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to read LinkedIn profiles, company pages, jobs, messages, and feed through a user's logged-in browser session.19Apache 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
TDQS
Scored across 21 tools
Each tool targets a distinct resource/action, and overlapping-seeming areas are well separated by descriptions: get_feed vs search_posts vs get_company_posts, search_people vs get_company_employees, and get_inbox vs get_conversation vs search_conversations. The relationship between send_message and connect_with_person is also clear, despite the reply-path caveat.
Names follow a predictable snake_case verb_noun pattern throughout: get_*, search_*, connect_with_*, send_*, comment_on_*, and close_*. Minor variations like connect_with_person and comment_on_post still fit the convention.
The server covers a broad LinkedIn surface (jobs, profiles, companies, messaging, feed/posts, and session management), so 21 tools is defensible. It is slightly above the ideal 3-15 range but each tool has a clear role.
Coverage is broad across reading and some writing workflows, but there are notable lifecycle gaps: no safe reply to an existing message thread, no job application or save/unsave operation, and no post creation or reaction tools. Agents can still inspect and interact with many resources, but several common LinkedIn workflows are incomplete.