Mcp Linkedin Post Engager Capture

com.mambabuilt由 mambabuilt.com 發布v1.4.1更新於 Nov 7, 2026

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

概覽

AI 產生的概覽

封裝 Apify actor,依指定的個人檔案或公司頁面回傳搜尋引擎已索引的 LinkedIn 貼文,並以扁平列輸出。

可以做什麼
  • 蒐集 LinkedIn 個人檔案與公司頁面被索引的貼文
  • 每篇貼文輸出一列:連結、作者、內文摘錄與發佈日期
  • 可依 posted_since 日期篩選,並用 max_charge_usd 限制花費
  • 結果中同時回傳執行層級與來源層級的提示列
適用情境
適合想快速取得特定人物或公司公開且被索引的 LinkedIn 貼文、又不想登入 LinkedIn 的情境。它並非完整存檔,涵蓋範圍取決於搜尋引擎索引的內容。
執行需求
透過 npx(Node.js)以 stdio 在本機執行。需要 Apify 帳號與 APIFY_TOKEN 環境變數,並需能連線至 Apify;不使用 LinkedIn 帳號或 Cookie。
安裝前請注意
依蒐集到的貼文數量計費,另加少量 actor 啟動費,執行會產生費用,建議設定 max_charge_usd 與 posted_since 控制支出。結果包含具名個人的個人資料,README 指出你為資料控管者。此 actor 為非官方,與 LinkedIn 無關聯,且涵蓋範圍不完整。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Linkedin Post Engager Capture,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源:README.md,提交 9fe4d93

工具

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.

輸入參數company_urlsposted_sinceprofile_urlsmax_charge_usd

版本歷史

7
  1. v1.4.1最新Nov 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

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分