Skip to main content
Glama
nitishnaidi

LinkedIn MCP

by nitishnaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to LinkedIn MCP

No user-submitted related servers found.

    Related Servers

    • LinkedIn Actions MCP

      leandrojacome
      A
      license
      B
      quality
      C
      maintenance
      Enables publishing text or image posts to LinkedIn through the official API and preparing or submitting simplified job applications using a secure local browser session, with user confirmation and privacy safeguards.
      2
      Apache 2.0

    • linkedin-local-mcp

      condr-at
      A
      license
      A
      quality
      B
      maintenance
      Enables local-only use of LinkedIn's official API to authenticate via OAuth, publish text posts, and read or reply to comments with explicit confirmation. Keeps access tokens in the OS keychain and avoids scraping or browser automation.
      4
      MIT

    • linkedin-mcp

      nadirzhon
      A
      license
      A
      quality
      C
      maintenance
      Enables publishing and scheduling LinkedIn posts through the official API, with content calendar and post brief tools for consistent growth.
      7
      MIT

    • linkedin-post-mcp

      Yousef200188
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to create and manage LinkedIn posts via OAuth, including text posts, URL shares, deletions, profile lookup, and company page posting.
      6 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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connection status, OAuth start, OAuth completion, post preparation, and post publishing. There is no overlap between these operations, and the prepare/publish distinction is explicit. An agent can easily select the right tool for each step.

    Naming Consistency4/5

    All tool names are snake_case and share the 'linkedin_' prefix, and four use a verb_noun pattern (start/complete/prepare/publish). The one exception is 'linkedin_connection_status', which uses a noun phrase instead of 'get_connection_status', a minor deviation. Overall the pattern is predictable and readable.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a LinkedIn publishing/OAuth workflow. It covers the essential steps without unnecessary redundancy, and the count is typical for a focused integration server.

    Completeness4/5

    The tools cover the full intended workflow: connection status, OAuth initiation/completion, post preparation, and post publishing. Minor gaps exist (e.g., no explicit disconnect or post-history tool), but these do not break the core human-in-the-loop publishing flow the server is designed for.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources