Mcp Sequencer Event Poller

Sequencer Event Poller MCP Server

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

[Sequencer Event Poller MCP server]

An 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.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

What it does

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.

Quick start

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.

Prerequisites

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.
• At least one of your own vendor keys: 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.

Example prompts

• "Which leads replied in Smartlead or lemlist in the last 24 hours?"
• "List every bounce and unsubscribe across my sequencers this week."
• "Who replied on LinkedIn through HeyReach since Monday, and what did they say?"

Tool

poll_sequencer_events. One tool. Example arguments:

{  "since_hours": "24",  "event_types": ["reply", "linkedin_reply", "bounce", "meeting_booked"]}

Inputs

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. Numbers and yes or no options are sent as text ("24", "true"), which is what the actor accepts; a value that does not parse comes back as one free row that names the field.

Pricing

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.

Your keys

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.

Full actor documentation

apify.com/mambalabs/sequencer-event-poller

License

MIT. See LICENSE.