MCP Linkedin Post Engager Capture

What mcp-linkedin-post-engager-capture does

mcp-linkedin-post-engager-capture is a thin MCP wrapper around Mamba Labs’ LinkedIn Post Tracker and Comment Capture actor on Apify. It accepts lists of LinkedIn person-profile URLs, company-page URLs, or both, then returns the actor’s dataset without changing its contents.

The results cover recent posts, including author information, text, media, permalink, publication time, reaction count, and comment count. When enabled, commenter rows contain the commenter’s name, profile URL, and comment text. Posts and commenters are stored as separate row types in one dataset, joined through post_id.

How it works

The server exposes one tool: capture_linkedin_posts_and_commenters. Its optional inputs include profile_urls, company_urls, posted_since, collect_commenters, collect_reactors, max_engagers_per_post, and use_residential_proxy.

posted_since accepts an ISO date and excludes older posts before actor events are charged. Commenter collection defaults to enabled. The commenter limit accepts values from 0 to 100, but LinkedIn generally exposes only about ten top-level commenters to logged-out visitors, so values above 10 do not increase the visible result set. Setting the limit to 0 collects posts without commenter charges.

The output uses row_type values of post, engager, and notice. A post’s post_id is intended to remain stable across runs, country subdomains, and supported permalink forms. Rows also include degradation fields so consumers can distinguish unavailable data from an observed absence.

Setup and configuration

Install the package with:

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

Set the APIFY_TOKEN environment variable with a token from Apify. The README provides a Claude Desktop configuration that starts the package through npx and passes this variable in the server environment. The server consumes Apify credits when it starts runs.

No LinkedIn account, session cookie, or LinkedIn credential is required. The Apify actor reads information served to logged-out visitors. If neither URL list is supplied, the tool returns a no_input notice row rather than failing.

Tools and capabilities

• Capture posts from LinkedIn person profiles and company pages.
• Include publicly visible commenter rows or collect posts only.
• Apply a publication-date cutoff before collection is charged.
• Return reaction and comment counts on post rows.
• Use post_id to associate commenters with their posts.
• Optionally request residential proxy use through the actor.

Limitations and notes

mcp-linkedin-post-engager-capture cannot retrieve commenter coverage beyond what logged-out LinkedIn displays. Measurements in the README show that visible commenters can represent only a small fraction of the actual comment total, and some commenter rows have no timestamp. Each post includes collected and available commenter counts to expose this coverage.

Individual reactor identities are not returned. The actor reports reaction totals, while reactors_status indicates that reactor identities are unavailable without login; changing collect_reactors does not produce reactor rows.

There is no result cache, so each run fetches the sources again. Billing includes collected posts, collected commenters, and an actor-start fee; notice rows are free. Invalid input, invalid or exhausted Apify credentials, timeouts, and non-dataset actor results are surfaced as explicit tool errors.

The tool returns named-person commenter data. Users are responsible for determining an appropriate lawful basis for handling that personal data. The actor is unofficial and is not affiliated with LinkedIn or Microsoft.