Mcp Linkedin Post Engager Capture

com.mambabuiltPublished by mambabuilt.comv1.4.1Updated Nov 7, 2026

Collect the LinkedIn posts a search engine has indexed for profiles and company pages.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Wraps an Apify actor that returns LinkedIn posts a search engine has indexed for given profiles or company pages, as flat rows.

What you can do
  • Collect indexed posts for LinkedIn person profiles and company pages
  • Return one row per post with permalink, author, text excerpt and publish date
  • Filter by posted_since date and cap spending with max_charge_usd
  • Surface run-level and source-level notice rows alongside results
When to use it
Use it when you want a quick, low-effort list of publicly indexed LinkedIn posts from specific people or companies, without logging into LinkedIn. It is not a complete archive: coverage depends on what the search index holds.
Requirements
Runs locally via npx (Node.js) over stdio. Requires an Apify account and an APIFY_TOKEN environment variable. Network access to Apify is needed; no LinkedIn account or cookie is used.
Before you install
Usage is billed per post collected plus a small actor start fee, so runs cost money; set max_charge_usd and posted_since to limit spend. Results contain personal data about named individuals, and the README states you are the data controller. The actor is unofficial and unaffiliated with LinkedIn, and coverage is incomplete.

Installation

In SourceWeft

  1. Open Mcp Linkedin Post Engager Capture in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

LinkedIn Post Tracker MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[LinkedIn Post Engager Capture MCP server]

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

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

Claude Desktop

json
{  "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, the posts a search engine has indexed for them out.

InputTypeRequiredMeaning
profile_urlsarray of stringsone of the twoPerson profiles, for example https://www.linkedin.com/in/williamhgates.
company_urlsarray of stringsone of the twoCompany pages, for example https://www.linkedin.com/company/microsoft.
posted_sincestringnoISO date. Posts published before this are skipped before anything is charged.
max_charge_usdnumbernoSpend cap for the run, in USD. The run starts no post whose charge would cross it and writes one max_charge_reached notice row.

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.

EventPrice per event (USD)Fires when
apify-actor-start$0.00005Charged 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 plansOne 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.

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.

Source

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

Built by Mamba Labs

Source: README.md at commit 9fe4d93

Tools

1

capture_linkedin_posts_and_commenters

Capture LinkedIn Posts and Commenters

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.

Parameterscompany_urlsposted_sinceprofile_urlsmax_charge_usd

Version history

7
  1. v1.4.1LatestNov 5, 2026
  2. v1.4.0Oct 16, 2026
  3. v1.3.1Oct 16, 2026
  4. v1.3.0Oct 12, 2026
  5. v1.2.1Oct 6, 2026
  6. v1.2.0Oct 6, 2026
  7. v1.1.0Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts