MCP server for the Mamba Labs LinkedIn Post Tracker and Comment Capture actor on Apify. Profiles and company pages in, their recent posts with real engagement counts out, plus the commenters LinkedIn shows publicly. No cookies, no account.
claude mcp add mcp-linkedin-post-engager-capture -- npx -y mcp-linkedin-post-engager-capture
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · mambalabsdev/mcp-linkedin-post-engager-capture · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository mambalabsdev/mcp-linkedin-post-engager-capture;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
MCP server for the Mamba Labs LinkedIn Post Tracker actor on Apify. Point it at LinkedIn person profiles or company pages. It returns the posts a search engine has indexed for each one, as flat rows: permalink, author, a text excerpt, and the publish date. No request is sent to LinkedIn, and no cookie, account, or credential is used. **Changed in 1.3.0.** The actor stopped fetching linkedin.com on 2026-10-12. Commenter rows, reaction and comment counts, media, and the inputs collect_commenters, collect_reactors, max_engagers_per_post, and use_residential_proxy are gone. Posts now come from search results, so coverage is what the index holds: posts appear days or weeks after publishing, and many never appear. The tool keeps its name, capture_linkedin_posts_and_commenters, so existing clients keep working. Install Claude Desktop Get an Apify token at console.apify.com/account/integrations. Tool capture_linkedin_posts_and_commenters LinkedIn profiles and company pages in, the posts a search engine has indexed for them out. | Input | Type | Required | Meaning | |---|---|---|---| | profile_urls | array of strings | one of the two | Person profiles, for example https://www.linkedin.com/in/williamhgates. | | company_urls | array of strings | one of the two | Company pages, for example https://www.linkedin.com/company/microsoft. | | posted_since | string | no | ISO date. Posts published before this are skipped before anything is charged. | Reading the output - post is one row per indexed post: post_id, post_permalink, author_name, author_url, author_type, post_text (the search engine's excerpt), published_at (decoded from the post id). - notice is a run-level or source-level message. Filter these out before loading a table. A post counts only when its permalink names the source, for example linkedin.com/posts/stripe_... for linkedin.com/company/stripe. A refused search comes back as a degraded notice, never as "no posts". Billing You are charged per post collected, plus a small actor start fee. Notice rows are free. posted_since filters before anything is charged. | Event | Price per event (USD) | Fires when | | --- | --- | --- | | apify-actor-start | $0.00005 | Charged when the Actor starts running, one event per GB of memory. | | post-collected | $0.002 on the Free plan, down to $0.0017 on higher Apify plans | One LinkedIn post returned from search results, with its permalink, author, text excerpt and publish date. | The actor's Apify page carries the current prices. 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.