Skip to main content
Glama
AmmYoo7

linkedin-safe-mcp

by AmmYoo7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to linkedin-safe-mcp

No user-submitted related servers found.

    Related Servers

    • 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 Buddy

      sigvardt
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn automation that enables AI agents to perform LinkedIn actions (search, inbox, feed, jobs, etc.) safely with human-like evasion and two-phase commit preview.
      2 npm
      2
      MIT

    • SalesTouch

      antoineDsh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT

    • linkedin_mcp

      devleads
      F
      license
      A
      quality
      C
      maintenance
      MCP server for automating LinkedIn actions such as reading feeds, sending messages, creating posts, and managing connections. Uses browser automation with proxy and stealth support.
      21
      -

    • 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

    A4.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: auth, profile, posts, comments/likes, job search, and local job tracking are cleanly separated. Even similar pairs like get_job vs get_saved_job are disambiguated by explicit descriptions.

    Naming Consistency4/5

    The majority follow a clear verb_noun pattern (create_post, delete_post, search_jobs, get_saved_job, update_job_status). Minor deviations like auth_status and login/logout break the pattern slightly but remain intuitive.

    Tool Count4/5

    At 16 tools the server is slightly above the ideal 3-15 range, but the count is justified by covering authentication, LinkedIn social actions, job search, and a local job tracker. Each tool serves a concrete purpose.

    Completeness5/5

    The surface covers the full workflow: auth lifecycle, profile retrieval, post creation/deletion, commenting/liking, job searching/details, and complete CRUD plus notes/status tracking for saved jobs. There are no significant dead ends or missing core operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources