接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @mambalabsdev/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
APIFY_TOKEN=<secret> claude mcp add com.mambabuilt-mcp-linkedin-post-engager-capture -- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture@1.4.1在終端機中執行。
{ "mcpServers": { "com.mambabuilt-mcp-linkedin-post-engager-capture": { "command": "npx", "args": [ "-y", "@mambalabsdev/[email protected]" ], "env": { "APIFY_TOKEN": "<secret>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
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.
capture_linkedin_posts_and_commentersLinkedIn profiles and company pages in, the posts a search engine has indexed for them out.
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.
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
Collect the LinkedIn posts a search engine has indexed for profiles and company pages.
{ "mcpServers": { "com.mambabuilt-mcp-linkedin-post-engager-capture": { "command": "npx", "args": [ "-y", "@mambalabsdev/[email protected]" ], "env": { "APIFY_TOKEN": "<secret>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:APIFY_TOKEN。
MCP Linkedin Post Engager Capture 透過 stdio 在本機執行。
上次檢查時間:2026-11-11。 Collect the LinkedIn posts a search engine has indexed for profiles and company pages.