Skip to main content
Glama
sviera91

linkedin-mcp-server

by sviera91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to linkedin-mcp-server

No user-submitted related servers found.

    Related Servers

    • LinkedIn Poster MCP

      codebytemirza
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets you publish text and image posts to LinkedIn, fetch your profile, and check auth status using natural language.
      MIT

    • @mhdd_24/linkedin-mcp

      Mhdd-24
      A
      license
      A
      quality
      C
      maintenance
      MCP server that posts to LinkedIn through the LinkedIn API. Enables creating text posts on your LinkedIn profile using natural language from any MCP-compatible client.
      3
      ISC

    • linkedin-mcp-server

      Selangwe
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that posts PDF/carousel content to a personal LinkedIn profile via LinkedIn's official REST API. It handles OAuth and provides tools to upload documents and publish posts.
      74 npm
      1
      MIT

    • linkedin-mcp-oauth

      zecloud
      A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for LinkedIn hosted on Azure Functions, enabling profile retrieval and post publishing through OAuth.
      74 npm
      MIT

    • Networking MCP

      otnielba
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct concern: authentication status, authentication initiation, profile retrieval, and post creation. There is no overlap in purpose.

    Naming Consistency5/5

    All tools use a consistent 'linkedin_' prefix followed by a clear verb_noun pattern (auth_status, authenticate, get_my_profile, create_post). Naming is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for a LinkedIn integration server covering authentication, profile access, and posting. Each tool earns its place without redundancy.

    Completeness4/5

    The core workflow of authenticating, reading profile, and creating posts is covered. Minor gaps exist (e.g., no post deletion or feed reading), but these are not critical for the server's apparent primary purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources