Sequencer Event Poller MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required for tool calls. | |
| LEMLIST_API_KEY | No | Your own lemlist API key. | |
| HEYREACH_API_KEY | No | Your own HeyReach API key. | |
| INSTANTLY_API_KEY | No | Your own Instantly API v2 key with read scope. | |
| SMARTLEAD_API_KEY | No | Your own Smartlead API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| poll_sequencer_eventsA | Read replies, bounces, unsubscribes, meetings booked, interest changes, and LinkedIn replies from your own Instantly, Smartlead, HeyReach, and lemlist accounts for a time window. Returns one flat row per event (vendor, event type, time, lead email and name, company, campaign, reply text where the vendor returns it) plus one free run summary row with counts and the status of each vendor. Vendor keys are read from this server's environment (INSTANTLY_API_KEY, SMARTLEAD_API_KEY, HEYREACH_API_KEY, LEMLIST_API_KEY); vendors with no key are skipped. Read-only: it never creates, edits, pauses, or sends anything in a sequencer. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and is billed per event row. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the server, there is no possibility of misselection or overlap. Its purpose is clearly stated and distinct.
The single tool follows a clear snake_case verb_noun convention: poll_sequencer_events. There are no competing conventions to conflict with it.
A single tool is reasonable for a narrow read-only event poller, and it consolidates multiple vendors into one operation. However, having only one tool is on the thin side for the apparent breadth of vendor/event-type handling.
The tool covers reading events across all supported vendors, includes summary/status information, and correctly excludes write operations since it is read-only. Minor gaps remain around filtering by vendor/event type and handling large result sets via pagination.