Skip to main content
Glama
mdnaimul22

LinkedIn MCP Pro Max

by mdnaimul22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LinkedIn MCP Pro Max

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp-server

      vahabcore
      A
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP server that enables AI agents to autonomously create, manage, and engage with LinkedIn content through the official LinkedIn REST API.
      74 npm
      2
      MIT

    • LinkedIn MCP Server

      selvin-paul-raj
      A
      license
      A
      quality
      D
      maintenance
      Fully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.
      6
      3
      MIT

    • LinkedIn MCP

      Eldasoky1
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for programmable LinkedIn automation via Playwright, offering 20 tools for profile management, messaging, feed interaction, and job searching through real browser automation.
      13 npm
      MIT

    • linkedin-mcp-pro

      horizonbymuneeb
      A
      license
      A
      quality
      C
      maintenance
      Self-hosted, ban-safe MCP server for LinkedIn that provides 22 tools for profiles, search, jobs, posts, connections, and messages. Integrates with any MCP-compatible client like Claude Desktop.
      58
      1
      MIT

    • openlinkedinmcp

      tiagoyamashita
      A
      license
      B
      quality
      C
      maintenance
      Playwright-powered MCP server for LinkedIn that automates jobs, profile edits, messaging, network actions, and feed posts using a real logged-in browser session.
      36
      Apache 2.0
    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.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., interact_with_post vs create_linkedin_post, job vs application). Some minor overlap exists between generate_resume and tailor_resume, but descriptions clarify the distinction. Profile and its sub-section tools (experience, skills, education) are logically separated but could be slightly ambiguous.

    Naming Consistency2/5

    Naming conventions are mixed: some tools are verb_noun (create_linkedin_post, generate_resume, list_templates), while others are bare nouns (job, profile, company, experience, skills, education, server, application). This inconsistency makes the tool set feel less predictable, even though the noun tools share a pattern of action-based arguments.

    Tool Count5/5

    With 14 tools, the server covers a broad but well-scoped set of LinkedIn features (posts, jobs, profiles, resumes, applications). The count is within the ideal 3-15 range and each tool addresses a meaningful function without redundancy.

    Completeness4/5

    The server covers core LinkedIn workflows: profile management (experience, skills, education), job search/apply, post creation/interaction, and resume/cover letter generation. Minor gaps exist, such as no post deletion or edit, and no direct messages/connections, but these are not critical for the apparent job-seeker focus.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources