Skip to main content
Glama
mambalabsdev

mcp-linkedin-post-engager-capture

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-linkedin-post-engager-capture

No user-submitted related servers found.

    Related Servers

    • LinkedIn Data API MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to comprehensive LinkedIn data, including professional profile details, company information, and social engagement metrics. It supports searching for people, retrieving posts and comments, and fetching detailed experience, skills, and recommendations.
      52
      MIT

    • LinkedIn Posts API

      johnisanerd
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and fetch LinkedIn posts with engagement metrics (reactions, comments, shares) and author details, returning structured JSON per post.
      -
    • inprofile by boxed-dev

      inprofileofficial

      boxed-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading LinkedIn profiles into structured JSON using your own signed-in session, with no browser automation or API keys.
      MIT

    • LinkedIn Scraper MCP Server

      superyuser
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables extraction of comprehensive LinkedIn profile data including experience, education, skills, and contact information through browser automation. Requires manual LinkedIn credentials input and uses anti-detection measures for reliable scraping.
      5
      -
    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.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity between tools. The purpose is clearly described.

    Naming Consistency5/5

    The single tool name follows a descriptive verb_noun pattern and clearly indicates its action and target. Consistency is not a concern with only one tool.

    Tool Count3/5

    A single tool is on the borderline of being too thin for a server, even if it encapsulates a complex workflow. The tool is comprehensive in scope but represents only one function under the server's 'engage' name.

    Completeness2/5

    The tool captures posts and commenters but explicitly lacks reactor identities and has limited comment coverage, despite the server name suggesting engagement capabilities. This leaves significant gaps in the stated purpose of engaging with LinkedIn content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources