Skip to main content
Glama
bartest5

MCP Server for LinkedIn

by bartest5

Related Servers

Alternatives to MCP Server for LinkedIn

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.8/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: messaging (get_inbox, search_conversations, get_conversation, send_message), profiles (get_my_profile, get_person_profile, get_sidebar_profiles), companies (get_company_profile, get_company_posts, search_companies, get_company_employees), jobs (search_jobs, get_job_details), and general actions (search_people, connect_with_person, get_feed, close_session). Even similarly named tools like get_inbox and get_conversation have clear boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_, search_, connect_, send_, close_. The verbs are simple and the nouns clearly indicate the target resource, making the pattern predictable and easy to learn.

    Tool Count4/5

    With 17 tools, this is slightly above the typical 'sweet spot' of 3-15, but the count is justified by the broad scope of LinkedIn (profiles, companies, jobs, messaging, feed). Each tool serves a distinct function and none feel redundant, so the size is reasonable though a bit heavy.

    Completeness4/5

    The tool surface covers core LinkedIn workflows: searching and viewing profiles, companies, jobs, messaging, and feed. However, some common actions are missing, such as updating a profile, posting content, liking/sharing posts, or managing connections beyond sending requests. These gaps are workable but notable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues