Linkedin Post Engager Capture MCP Server

LinkedIn Post Tracker and Comment Capture MCP Server

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.

Tool

capture_linkedin_posts_and_commenters

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

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