pushengage_send_notification
Sends or schedules a notification. One tool, three delivery modes: send now, one-shot schedule (optionally per-subscriber timezone), and recurring. Optional audiencegroups targeting; otherwise all subscribers.
How to use it
pushengage_send_notification is exposed by the Pushengage MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the pushengage_send_notification tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL PUSHENGAGE MCP LISTINGOther tools in Pushengage MCP (14)
Opens the browser to PushEngage and stores the token on success.
Deletes the locally stored token.
Shows whether you are authenticated and which site is selected.
Lifetime totals: subscribers, notifications sent, views, clicks, and goal count/value.
Per-bucket (day/week/month) subscribers, sends, views, clicks, CTR, and unsubscribes over a date range.
The on-site widget that surfaces WhatsApp, Messenger, and other channels. Shows status, channels, devices, business-hours restriction, and targeting.
Drip autoresponders. Filter by status; set includeanalytics for per-campaign stats.
Lists sent, scheduled, and draft notifications, newest first. Filter by status (dashboard-tab semantics), sent-date range, or tags; set includeanalytics for rolled-up A/B and timezone-send stats.
RSS auto push campaigns. Filter by status.
Lists the PushEngage sites you can access.
Triggered campaigns (cart/browse abandonment, price drop, etc.). Filter by status; optional analytics.
Workflow automations. Filter by status; set includeanalytics for entered/active/completed/failed and goal stats.
Sets the current site used by the other tools.
An A/B notification with two variants. Pass intelligentabtest to sample each variant, pick the winner by click rate after a delay, and roll the winner out to the rest.