Skip to main content
Glama
mambalabsdev

mcp-linkedin-post-engager-capture

by mambalabsdev

LinkedIn Post Tracker and Comment Capture MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

MCP server for the Mamba Labs LinkedIn Post Tracker and Comment Capture actor on Apify.

Point it at LinkedIn person profiles or company pages. It returns their recent posts as flat rows, with the real reaction and comment counts on every one, plus the commenters LinkedIn shows publicly. No cookies, no LinkedIn account, no credentials of any kind.

Install

npx -y @mambalabsdev/mcp-linkedin-post-engager-capture

Claude Desktop

{
  "mcpServers": {
    "mamba-linkedin-post-engager-capture": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-linkedin-post-engager-capture"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Get an Apify token at console.apify.com/account/integrations.

Related MCP server: LinkedIn Data API MCP Server

Tool

capture_linkedin_posts_and_commenters

LinkedIn profiles and company pages in, their recent posts and public commenters out.

Input

Type

Required

Notes

profile_urls

array

no

Person profiles, for example https://www.linkedin.com/in/williamhgates. Country subdomains are fine. Supply this, company_urls, or both.

company_urls

array

no

Company pages, for example https://www.linkedin.com/company/microsoft. Supply this, profile_urls, or both.

posted_since

string

no

ISO date, for example 2026-08-01. Posts older than this are skipped before anything is charged.

collect_commenters

boolean

no

One row per public commenter. Turn it off to collect posts only. Default true.

collect_reactors

boolean

no

Returns no reaction rows whatever you set, because LinkedIn serves no reactor identities to a logged-out visitor. Present so the limit is visible rather than silent. Default true.

max_engagers_per_post

integer

no

0 to 100. Ten is LinkedIn's own ceiling for a logged-out visitor, so raising it above 10 does nothing. Set it to 0 to pay for posts only. Default 10.

use_residential_proxy

boolean

no

Off by default, which is what the pricing assumes. Apify bills residential bandwidth on top of this actor's events. Default false.

Nothing is required. A call with neither URL list comes back as a no_input notice row rather than an error, which mirrors the actor exactly.

Reading the output

One dataset carries three row types, told apart by row_type. Filter on it before loading a table.

  • post is one row per LinkedIn post.

  • engager is one row per public commenter, joined to the post on post_id.

  • notice is a run-level or source-level message.

post_id is the numeric part of LinkedIn's activity URN. It is stable across runs, across country subdomains and across both permalink spellings, so it is safe as a primary key and safe as the "have I already posted this to Slack" check.

The commenter limits are real and they are not small. LinkedIn renders about ten top-level comments to a logged-out visitor whatever the true total. Measured whole-run coverage was 178 commenters out of 4,857 that existed, which is 3.7 percent. About 30 percent of comment rows carry no timestamp. Every post row carries commenters_collected beside commenters_available so the coverage on any given post is a number you can read rather than something you infer.

Reactor identities are not available at all to a logged-out visitor. Every post row still carries the real reaction_count, and reactors_status says unavailable_without_login.

Every row carries degraded and degradation_reason. false means the actor looked; null on a field means it could not. Filter on degraded before you trust an absence. Two things that look like failures are deliberately not degraded, because both are measurements: reactors_unavailable is how logged-out LinkedIn works, and no_posts_found on a page that loaded is a real absence.

Billing

You are charged per post collected and per commenter collected, plus a small actor start fee. Notice rows are free. posted_since filters before anything is charged, so a scheduled run that finds nothing new costs the actor start and nothing else.

There is no result cache: every run refetches, which is the right behavior for an actor whose job is to notice new posts. Pricing is on the actor's Apify page. Running this server consumes Apify credits.

What this server does and does not do

It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.

It reads only what LinkedIn serves to a logged-out visitor. It holds no session cookie, uses no LinkedIn account, and reads nothing behind a login.

Commenter rows are named people. When you run this you are the data controller for the personal data it returns and Apify is the processor. Your lawful basis is yours to establish; nothing here is legal advice.

This actor is unofficial and is not affiliated with, sponsored by or endorsed by LinkedIn or Microsoft.

Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.

Source

The actor is on the Apify Store. This wrapper is MIT licensed.

Built by Mamba Labs

Install Server
A
license - permissive license
A
quality
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

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

View all related MCP servers

Related MCP Connectors

  • Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.

  • Live LinkedIn data for AI agents: profiles, companies, jobs, posts, email finding. No account risk.

  • LinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-linkedin-post-engager-capture'

If you have feedback or need assistance with the MCP directory API, please join our Discord server