Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @mambalabsdev/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
APIFY_TOKEN=<secret> claude mcp add com.mambabuilt-mcp-linkedin-post-engager-capture -- npx -y @mambalabsdev/mcp-linkedin-post-engager-capture@1.4.1Execute em um terminal.
{ "mcpServers": { "com.mambabuilt-mcp-linkedin-post-engager-capture": { "command": "npx", "args": [ "-y", "@mambalabsdev/[email protected]" ], "env": { "APIFY_TOKEN": "<secret>" } } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirMCP 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>" } } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
O publicador lista estas variáveis de ambiente: APIFY_TOKEN.
MCP Linkedin Post Engager Capture roda localmente via stdio.
Última verificação: 2026-11-11. Collect the LinkedIn posts a search engine has indexed for profiles and company pages.