Skip to main content
Glama

Related Servers

Alternatives to Link

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables posting content, sharing articles, and managing your LinkedIn profile through Claude using the official LinkedIn API with OAuth 2.0.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to manage your LinkedIn profile and company pages, including posting, reading posts, and fetching profile information.
      7
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Post to LinkedIn from Claude — create posts, upload images, edit/delete posts, and manage company pages via natural language. Uses the official LinkedIn REST API with OAuth 2.0.
      9
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to check LinkedIn connection status, publish approved posts to a LinkedIn feed, and delete posts published through the connector.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a distinct step in a clear workflow: check/list/next/mark/summary for connections, next/mark/reply_open for inbox, publish/comment for posting, and status for auth. The only real overlap is connections_check versus connections_check_list, which the descriptions separate by lane (single profile vs. up to 40 list rows), and connections_next versus connections_list/summary, which are distinguished by pacing/queue vs. paging vs. aggregates. Minor ambiguity remains around when to use check_list instead of check.

    Naming Consistency4/5

    Mostly a consistent noun_verb pattern grouped by namespace: connections_*, inbox_*, post_publish, comment_create, archive_load, reply_open. Deviations are small: linken_status uses a misspelled domain prefix unlike any other tool, and connections_check_list is the only three-token name.

    Tool Count5/5

    13 tools sit comfortably in the well-scoped range and each maps to a distinct stage of the connections, inbox, or publishing lifecycle. Nothing looks redundant or padded; the safety primitives (caps, halt file, dry-run) are exposed through existing tools rather than one tool each.

    Completeness4/5

    The surface covers the full loop: archive_load → connections_list/check/check_list → connections_mark → connections_next, plus inbox_next/inbox_mark/reply_open and post_publish/comment_create, with status for diagnostics. Gaps are minor and mostly deliberate (no LinkedIn-side removal, no scheduling/edit/delete, no text search over connections), but the absence of search by name/company could force agents to page through results.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues