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> INSTANTLY_API_KEY=<secret> SMARTLEAD_API_KEY=<secret> HEYREACH_API_KEY=<secret> LEMLIST_API_KEY=<secret> claude mcp add com.mambabuilt-mcp-sequencer-event-poller -- npx -y @mambalabsdev/mcp-sequencer-event-poller@1.0.2Execute em um terminal.
{ "mcpServers": { "com.mambabuilt-mcp-sequencer-event-poller": { "command": "npx", "args": [ "-y", "@mambalabsdev/[email protected]" ], "env": { "APIFY_TOKEN": "<secret>", "INSTANTLY_API_KEY": "<secret>", "SMARTLEAD_API_KEY": "<secret>", "HEYREACH_API_KEY": "<secret>", "LEMLIST_API_KEY": "<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.
AbrirAn MCP server for the Mamba Labs Sequencer Event Poller actor on Apify. It reads replies, bounces, unsubscribes, meetings booked, interest changes, and LinkedIn replies from your own Instantly, Smartlead, HeyReach, and lemlist accounts, and returns one flat row per event.
Pick a time window, for example the last 24 hours, and get every event from the sequencers you have keys for in one table: vendor, event type, when it happened, the lead's email, name, and company, the campaign, and the reply text where the vendor returns it. One free run summary row gives counts per vendor and event type and says whether each vendor was read, skipped, or refused the key. With only new events on, a scheduled run returns only events an earlier run has not returned.
The actor only reads. It never creates, edits, pauses, or sends anything in a sequencer, and it never creates a campaign.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-sequencer-event-poller": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-sequencer-event-poller"
],
"env": {
"APIFY_TOKEN": "your-apify-token",
"LEMLIST_API_KEY": "your-lemlist-key"
}
}
}
}
Restart the client. The poll_sequencer_events tool appears.
APIFY_TOKEN. The server lists its tool without a token; a call needs one.INSTANTLY_API_KEY (API v2, read scope; Instantly API access needs a paid Instantly plan), SMARTLEAD_API_KEY, HEYREACH_API_KEY, LEMLIST_API_KEY. With none set, a call returns one summary row that says no key was given.poll_sequencer_events. One tool. Example arguments:
{
"since_hours": 24,
"event_types": ["reply", "linkedin_reply", "bounce", "meeting_booked"]
}
Every buyer facing input of the actor except the four vendor keys, which are read from this server's environment, never from tool arguments. Omitted inputs take the actor's own defaults.
Pay per event on Apify, billed to your Apify account. Prices in USD.
The run summary row and already delivered events are free. Mamba Labs pays the platform costs of the run.
The actor stores no key. Each vendor key is your own: this server reads it from its environment and sends it in the run input of that run only. The vendor API calls run on your own vendor account, under that vendor's plan and rate limits.
MIT. See LICENSE.
Replies, bounces, meetings, and LinkedIn replies from Instantly, Smartlead, HeyReach, and lemlist
{ "mcpServers": { "com.mambabuilt-mcp-sequencer-event-poller": { "command": "npx", "args": [ "-y", "@mambalabsdev/[email protected]" ], "env": { "APIFY_TOKEN": "<secret>", "INSTANTLY_API_KEY": "<secret>", "SMARTLEAD_API_KEY": "<secret>", "HEYREACH_API_KEY": "<secret>", "LEMLIST_API_KEY": "<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, INSTANTLY_API_KEY, SMARTLEAD_API_KEY, HEYREACH_API_KEY, LEMLIST_API_KEY.
MCP Sequencer Event Poller roda localmente via stdio.
Última verificação: 2026-11-11. Replies, bounces, meetings, and LinkedIn replies from Instantly, Smartlead, HeyReach, and lemlist