Wraps an Apify actor to collect search-engine-indexed LinkedIn posts for specified person profiles and/or company pages.
Accepts profile_urls, company_urls, or both.
Returns flat post rows with post_id, permalink, author details, text excerpt, publish date, row_type, and degradation fields.
Supports posted_since to skip older posts before charges are incurred.
Supports max_charge_usd as a spend cap, with a notice row when reached.
Requires filtering row_type to separate post rows from notice rows.
Uses only public search results; sends no request to LinkedIn and uses no cookie/account.
Requires APIFY_TOKEN and consumes Apify credits; errors are surfaced explicitly.
Does not return commenters, reaction counts, comment counts, or media.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-linkedin-post-engager-capture Show me recent posts and commenters from Bill Gates' LinkedIn"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
npx -y @mambalabsdev/mcp-linkedin-post-engager-capture{
"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
capture_linkedin_posts_and_commentersLinkedIn profiles and company pages in, the posts a search engine has indexed for them out.
Input | Type | Required | Meaning |
| array of strings | one of the two | Person profiles, for example |
| array of strings | one of the two | Company pages, for example |
| string | no | ISO date. Posts published before this are skipped before anything is charged. |
| number | no | Spend cap for the run, in USD. The run starts no post whose charge would cross it and writes one |
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".
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 |
| $0.00005 | Charged when the Actor starts running, one event per GB of memory. |
| $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.
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 public search engine results. It sends no request to LinkedIn, holds no session cookie, and uses no LinkedIn account.
Post rows from a person profile name that person. 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.
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Point it at LinkedIn person profiles or company pages and it returns the posts a search engine has indexed for each one, as flat rows: permalink, author, a text excerpt, and the publish date decoded from the post id. No request is sent to LinkedIn and no cookie or account is used. A result counts only when its permalink names the source, so posts are never attributed to the wrong author. Coverage is what the search index holds: posts appear days or weeks after publishing and many never appear. Commenters, reaction counts, comment counts and media are no longer returned (removed 2026-10-12, they came only from LinkedIn pages). Rows carry row_type post or notice; filter on row_type before loading a table. post_id is the activity URN and is stable across runs. Every row carries degraded and degradation_reason. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: company_urls, posted_since, profile_urls, max_charge_usd.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
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.
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.
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.
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.
Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.
LinkedIn companies, hiring signals and public profiles by URL. No login, no cookies. Pay per result.
LinkedIn intelligence: post analytics and research for public profiles and company pages.
Live LinkedIn data for AI agents: profiles, companies, jobs, posts, email finding. No account risk.
