Link
Related Servers
Alternatives to Link
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables posting content, sharing articles, and managing your LinkedIn profile through Claude using the official LinkedIn API with OAuth 2.0.6MIT
- AlicenseAqualityDmaintenanceEnables Claude to interact with LinkedIn for posting, commenting, sharing media, and viewing feed and profile.93MIT
- AlicenseAqualityDmaintenanceEnables Claude Desktop to manage your LinkedIn profile and company pages, including posting, reading posts, and fetching profile information.74MIT
- AlicenseAqualityDmaintenancePost 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.92MIT
- AlicenseNot gradedqualityDmaintenanceEnables posting text and media content directly to LinkedIn from Claude Desktop with support for authentication and visibility controls.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to check LinkedIn connection status, publish approved posts to a LinkedIn feed, and delete posts published through the connector.1MIT
TDQS
Scored across 13 tools
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.
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.
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.
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.