Skip to main content
Glama
SARAMALI15792

LinkedIn Custom MCP Server

by SARAMALI15792
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to LinkedIn Custom MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      VasquezRivero92
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage LinkedIn profiles, posts, connections, skills, education, certifications, and other professional data through the LinkedIn API.
      19
      MIT

    • LinkedIn MCP Server

      quinnjr
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage LinkedIn profiles, posts, connections, skills, education, and certifications through the LinkedIn API.
      18
      176 npm
      64
      MIT

    • LinkedIn MCP Server

      sandeepramdas
      A
      license
      B
      quality
      D
      maintenance
      Allows AI agents to authenticate with LinkedIn and share posts or links via the Model Context Protocol.
      2
      84 npm
      MIT

    • LinkedIn MCP Server

      himanshu31shr
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents with read/write access to LinkedIn API, including profile, posts, media, organizations, comments, reactions, and analytics.
      20
      10 npm
      MIT

    • LinkedIn MCP Server

      oliverhruby
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to authenticate with LinkedIn via OAuth, look up profiles and organizations, create and manage posts, comments, reactions, and media uploads, and handle ad campaign management, all with dry-run previews for write operations.
      34
      1
      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.7/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific LinkedIn resources and actions. For example, linkedin_create_post, linkedin_create_image_post, and linkedin_create_comment handle different content types, while search tools (companies, jobs, people) and get tools (profile, post details) are well-separated. No tools appear to overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'linkedin_verb_noun' pattern with snake_case throughout. The verbs are appropriate and predictable (e.g., create, delete, get, search, update), and nouns clearly indicate the resource (e.g., post, comment, profile). There are no deviations in naming conventions.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for a comprehensive LinkedIn API server covering posts, comments, profiles, companies, jobs, and OAuth. It includes core CRUD operations and search functionalities, though it might benefit from slight consolidation in some areas like OAuth-related tools.

    Completeness4/5

    The tool set provides strong coverage for LinkedIn's social and professional features, including create, read, update, delete for posts and comments, profile fetching, and searches. Minor gaps include lack of tools for liking/reacting to content or managing connections, but agents can perform core workflows effectively without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources