Skip to main content
Glama
mambalabsdev

mcp-linkedin-post-engager-capture

Related Servers

Alternatives to mcp-linkedin-post-engager-capture

No user-submitted related servers found.

    Related Servers

    • 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
    • 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.
      -
    • 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
    • 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
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables publishing text or image posts to LinkedIn through the official API and preparing or submitting simplified job applications using a secure local browser session, with user confirmation and privacy safeguards.
      2
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (capture indexed LinkedIn posts for given profiles/pages) is stated unambiguously.

    Naming Consistency4/5

    The single name uses a clear snake_case verb_noun form, which is internally consistent. However, it still advertises 'commenters' even though the description says commenter data was removed, making the name stale and slightly misleading.

    Tool Count3/5

    The server exposes exactly one tool for a very narrow, read-only capture operation, so the count is defensible but thin. An agent gets no separate means to list sources, filter row types, or fetch metadata without parsing the single flat output.

    Completeness4/5

    For a read-only 'capture posts from a search index' domain, one tool covers the whole lifecycle and returns stable post_id, row_type, and degradation flags. Gaps are minor: no dedicated source-validation or post-filtering operation, and the name's promise of commenters is no longer fulfilled.

    Maintenance

    ActivityActive
    ResponsivenessNo issues