Skip to main content
Glama
mcp-server-linkedin

mcp-server-linkedin

by gxm097

Related Servers

Alternatives to mcp-server-linkedin

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues