Skip to main content
Glama
dzigi00

LinkedIn Automation MCP Server

by dzigi00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LinkedIn Automation MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn Intelligence MCP

      southleft
      A
      license
      B
      quality
      D
      maintenance
      Connects Claude Desktop to LinkedIn's data layer for AI-powered networking, enabling profile research, content creation and scheduling, engagement automation, analytics tracking, and messaging through natural language.
      14
      85
      41
      MIT

    • @maheidem/linkedin-mcp

      Maheidem
      A
      license
      B
      quality
      D
      maintenance
      Integrates with Claude to enable LinkedIn post creation, profile optimization, content generation, and analytics through natural language.
      13
      8 npm
      1
      MIT

    • agentic-linkedin

      DarkLvrd
      A
      license
      B
      quality
      B
      maintenance
      Enables an AI agent to fully operate a LinkedIn account—posting, messaging, profile edits, and network management—with self-healing selectors, human-like pacing, and approval-based planning to avoid breakage or lockouts.
      39
      15 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.7/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: profiles, searches, messaging, feed, session, etc. Even the messaging-related tools (search_conversations, get_inbox, get_conversation, send_message) have clear, non-overlapping purposes. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_person_profile, search_jobs, send_message, close_session). The naming is predictable and easy to infer the function of each tool. Minor variations like 'connect_with_person' still fit the overall pattern.

    Tool Count4/5

    With 17 tools, the server is slightly above the ideal typical range of 3-15 but not excessive. Each tool covers a distinct aspect of LinkedIn automation, so the count is justified for the scope. It feels on the heavier side but still manageable.

    Completeness4/5

    The tools cover the primary LinkedIn automation domains: profiles (get, search), companies (search, profile, posts, employees), jobs (search, details), messaging (search, inbox, read, send), connections (send/accept), feed, and session management. Minor gaps exist such as no explicit 'reject connection' or 'create post', but these are not core for most automation workflows. Overall, the surface is well-rounded.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources