linkedin-mcp
Related Servers
Alternatives to linkedin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAllows Claude to execute terminal commands on your computer and perform file system operations including surgical code editing with diff-based replacements.197MIT
- AlicenseNot gradedqualityCmaintenanceEnables safe, reviewable updates to HackMD notes by preparing diffs locally, requiring explicit approval before writing, and verifying the result after the update.MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude to pull a live GitHub pull request's diff and CI check status and to post review findings back as comments on that PR, via three tools over stdio.-
- FlicenseNot gradedqualityDmaintenanceExposes functions to get the current working directory and review git diffs before commit as MCP tools, leveraging Claude Code CLI for diff review.-
- FlicenseNot gradedqualityDmaintenanceEnables surgical markdown edits across GitHub repositories through a claude.ai custom connector, batching multiple changes into exactly one commit.3-
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code to record a verifiable history of code changes with before/after and rationale, and to propose changes that users can accept or discard, all reviewable on a local web timeline.-
TDQS
Scored across 7 tools
Each tool has a distinct, unambiguous purpose: authentication start/status, profile retrieval, proposal creation, listing, discarding, and applying. No two tools overlap in function, and the descriptions clarify the exact role of each.
All tools follow a consistent verb_noun pattern (e.g., auth_start, get_profile, propose_edit, apply_proposal). The naming is uniform, predictable, and clearly indicates the action and target resource.
With 7 tools, the server is well-scoped for its purpose of LinkedIn profile editing. Each tool serves a necessary step in the workflow (auth, read, propose, manage, apply) without redundancy or bloat.
The tool surface covers the full lifecycle: authentication, profile reading, proposal creation with review, proposal management (list/discard), and the single write operation. The workflow is logically complete, and the explicit guardrails prevent dead ends.