A
licenseA
qualityB
maintenanceEnables 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.
21
Apache 2.0
LinkBridge MCP
Related Servers
Alternatives to LinkBridge MCP
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
- AlicenseAqualityCmaintenanceEnables 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.178,301 PyPI4,093Apache 2.0
- AlicenseAqualityBmaintenanceLets an AI assistant operate LinkedIn through an authenticated browser session, enabling profile management, posting, networking, messaging, job search, and automated applications.10012 npm1MIT
- 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
A3.7/5.0
Scored across 25 tools
Disambiguation4/5
Most tools target a clear resource+action, and the descriptions go out of their way to separate near-neighbors (send_message vs reply_to_conversation, get_feed vs search_posts vs get_company_posts, get_company_employees vs search_people). A few pairs still require reading long prose to distinguish, notably send_message/reply_to_conversation and get_job_apply_url/get_easy_apply_form/get_job_details, and get_sidebar_profiles overlaps conceptually with search_people.
Naming Consistency5/5
Every tool is snake_case with a verb-first pattern (get_*, search_*, send_*, reply_to_*, archive_*, close_*, dismiss_*, connect_with_*). No mixed casing or stylistic drift, and names are readable and predictable.
Tool Count4/5
25 tools is at the upper bound, but the LinkedIn domain is genuinely broad (people, companies, jobs, messaging, feed, session) and each tool maps to a distinct operation rather than being a variant of another. Slightly heavy, but the surface is defensible rather than padded.
Completeness4/5
Strong lifecycle coverage: profile reads, people/company/job/post search, connection requests, full messaging flow (inbox, read, search, reply, send, archive), job details/saved/dismiss, and session management. Gaps exist around writing actions — no save_job (only get_saved_jobs), no post creation/like/comment, no withdraw/remove connection, and Easy Apply is read-only with no submit path.
Maintenance
ActivityMaintained
ResponsivenessNo issues