linkedin-mcp-server
Related Servers
Alternatives to linkedin-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read LinkedIn profiles, company pages, jobs, messages, and feed through a user's logged-in browser session.19Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with LinkedIn by scraping profiles, companies, job postings, and getting personalized job recommendations using authenticated browser automation.1714,037 PyPI3,811Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to connect to LinkedIn, accessing profiles and companies, searching for jobs and people, managing saved jobs, updating job-search profile settings, and inspecting analytics.1Apache 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
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with LinkedIn using the official API for profile access, company management, and job postings.Apache 2.0
- AlicenseAqualityBmaintenanceLets an AI assistant operate LinkedIn through an authenticated browser session, enabling profile management, posting, networking, messaging, job search, and automated applications.10015 npm1MIT
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action: people, companies, jobs, messaging, and posts are clearly separated. Even the three post-related tools are explicitly differentiated by source (own feed, company page, global search), and the conversation tools distinguish list/read/search. No two tools appear to do the same thing.
All tool names use lowercase snake_case with a consistent verb-first pattern: get_*, search_*, connect_with_*, send_*, comment_on_*, and close_*. Longer noun phrases like get_sidebar_profiles and get_profile_post_urls still fit the verb_noun convention. There is no mixing of camelCase, acronyms, or inconsistent verb styles.
21 tools is on the heavy side, but the server covers a genuinely broad domain: profiles, companies, jobs, messaging, feed, posts, and session management. Each tool maps to a plausible distinct workflow, so the count feels justified rather than bloated. It is slightly above the ideal 3-15 range but not excessive for a full LinkedIn client.
The tool set covers the main LinkedIn surfaces well: people search/profile/connection, company profile/posts/employees, job search/details/saved, messaging, feed, and post commenting. Minor gaps remain, such as no ability to list the user's own connections, create a post, or like/react to content, but these are workaround enough for core recruiting/sales/researcher workflows. The included write tools (connect, message, comment) are balanced with the read tools.