Skip to main content
Glama
kyle-nelson-berkeley

linkedin-mcp

by kyle-nelson-berkeley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • LinkedIn Archive MCP

      nudavinci64
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to read your own LinkedIn profile directly from a local data export, with no API keys, OAuth, or scraping. Tools cover profile, positions, skills, posts, connections, and more, supporting editing drafts and cross-checking against résumés.
      MIT

    • linkedin-agent-mcp

      IzikStar
      A
      license
      A
      quality
      B
      maintenance
      Enables an MCP client such as Claude Code to search LinkedIn jobs, read postings and profile data, track what has been seen, and prepare actions on a user's own account. Every consequential LinkedIn action requires explicit out-of-band confirmation in a terminal, with typed tools and failure-honest errors.
      20
      1
      MIT

    • linkedin-mcp-server

      ihiteshgupta
      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
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources