pushengage-mcp
This MCP server lets an AI assistant manage a PushEngage account in plain language.
Authenticate via browser, check status, log out, list sites, and select the active site.
View and update site settings, campaign defaults, and service-worker settings.
Manage audiences: list/create segments, audience groups, subscriber attributes, and inspect site-specific filter values.
List drip, triggered, RSS, and workflow campaigns, plus chat widgets.
Inspect all-time analytics totals and date-range time-series analytics.
List sent, scheduled, and draft notifications with optional analytics.
Send, schedule, or create recurring push notifications, optionally per-subscriber timezone.
Send A/B notifications, including intelligent auto-winner tests.
Target sends to all subscribers, saved audience groups, or custom audience filters using segments, location, device, attributes, dates, and engagement.
@pushengage/mcp
Manage your PushEngage account from any AI assistant, in plain language.
PushEngage is a push notification platform for web push, mobile app push, WhatsApp, and on-site chat widgets, used to grow subscribers and recover revenue (cart abandonment, price drops, back-in-stock, and more).
This package is a Model Context Protocol (MCP) server. It connects MCP-capable assistants such as Claude Desktop, Claude Code, and Cursor to your PushEngage account so you can send and schedule notifications, run A/B tests, build audiences, inspect analytics, and manage site settings just by asking, without leaving your chat.
You log in once through your browser; the assistant then acts on your behalf against whichever PushEngage site you select.
Contents
Related MCP server: engain-mcp
What you can do
Once connected, just describe what you want. A few examples:
Send and schedule
"Send a notification titled 'Sale ends tonight', message 'Last call, 50% off', linking to https://example.com/sale."
"Schedule that for 9 AM in each subscriber's local timezone."
"Set up a recurring digest every Monday and Thursday at 8 AM through the end of the month."
"Run an A/B test of two headlines and auto-roll-out the winner by click rate."
Target the right people
"Create a segment for visitors of /pricing."
"Build an audience of gold-plan customers in the US and send only to them."
Understand performance
"How many subscribers do I have, and what was my click rate over the last 30 days?"
"List my active drip campaigns with their sent, seen, and clicked stats."
Configure a site
"Set my default notification expiry to 7 days."
"Change my site timezone to Asia/Kolkata and turn on geolocation."
Requirements
A PushEngage account (free or paid) with at least one site.
Node.js 20 or newer (the assistant runs the server via
npx).An MCP-capable client (Claude Desktop, Claude Code, Cursor, or any other).
Install
Add the server to your client's MCP config. No global install is needed; npx fetches it on demand.
Claude Desktop (one-click bundle)
The easiest path on Claude Desktop is the MCP Bundle:
Download the latest
pushengage-mcp-<version>.mcpbfile from the GitHub releases page.Open it with Claude Desktop (double-click it, or drag it onto the window) and click Install.
Everything is bundled — no JSON editing needed. The install dialog optionally lets you set the label shown on the PushEngage authorize screen and a custom token file path (for running multiple accounts).
Claude Desktop (manual config)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your platform:
{
"mcpServers": {
"pushengage": {
"command": "npx",
"args": ["-y", "@pushengage/mcp"]
}
}
}Restart Claude Desktop. The "pushengage" server should appear in your tool list.
Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"pushengage": {
"command": "npx",
"args": ["-y", "@pushengage/mcp"]
}
}
}Other MCP clients
Any client that speaks MCP over stdio works. Configure it to run the command npx -y @pushengage/mcp.
First run: logging in
Authentication is browser-based, so your credentials never touch the assistant.
Ask: "Log me into PushEngage." The server opens a browser tab to the PushEngage authorize page.
Click Authorize. The tab confirms success and an access token is saved locally.
Ask: "Show my PushEngage sites," then "Use site 12345" to pick the site to work with. The selection is remembered across restarts.
Every site-scoped tool acts on this current site unless you pass an explicit site_id. When the token expires you will see an AUTH_EXPIRED message; just ask to log in again.
Tools
All site-scoped tools default to the current site.
Authentication and sites
Tool | Purpose |
| Opens the browser to PushEngage and stores the token on success. |
| Shows whether you are authenticated and which site is selected. |
| Deletes the locally stored token. |
| Lists the PushEngage sites you can access. |
| Sets the current site used by the other tools. |
Site settings
Tool | Purpose |
| Site name, URL, timezone, geolocation, and the "Powered By PushEngage" branding toggle. |
| UTM parameters, fallback notification, fallback attributes, and default notification expiry. Updates merge over current values, so partial edits work. |
| Service worker registration, sub-folder support, and the worker file path. |
Audiences
Tool | Purpose |
| URL-rule based subscriber segments. |
| Saved targeting groups (device, country, segment, engagement, dates, attributes). Referenced by the send tools' |
| Custom subscriber attribute keys used in audience-group rules (max 50 per site). |
| The location and device values recorded on this site, with subscriber counts — the values a Custom Audience filter rule can use for |
Campaigns and automations
Tool | Purpose |
| Drip autoresponders. Filter by status; set |
| Triggered campaigns (cart/browse abandonment, price drop, etc.). Filter by status; optional analytics. |
| RSS auto push campaigns. Filter by status. |
| Workflow automations. Filter by status; set |
Chat widgets
Tool | Purpose |
| The on-site widget that surfaces WhatsApp, Messenger, and other channels. Shows status, channels, devices, business-hours restriction, and targeting. |
Analytics
Tool | Purpose |
| 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. |
Sending notifications
Tool | Purpose |
| Lists sent, scheduled, and draft notifications, newest first. Filter by status (dashboard-tab semantics), sent-date range, or tags; set |
| Sends or schedules a notification. One tool, three delivery modes: send now, one-shot schedule (optionally per-subscriber timezone), and recurring. |
| An A/B notification with two variants. Pass |
Configuration
No configuration is required — the server talks to PushEngage's production API out of the box. These environment variables are available for less common setups:
Env var | Default | Purpose |
|
| Label shown on the authorize screen as the requesting app. Set it if you want a specific label, e.g. |
|
| Where the token is stored. Set this to run more than one PushEngage account side by side (see below). Must be an absolute path — it's used exactly as given, with no |
Running multiple PushEngage accounts side by side
Register the server under two different names, each with its own PE_MCP_CONFIG_PATH so the tokens don't collide:
{
"mcpServers": {
"pushengage-client-a": {
"command": "npx",
"args": ["-y", "@pushengage/mcp"],
"env": {
"PE_MCP_CONFIG_PATH": "/Users/you/.pushengage/mcp-client-a.json",
"PE_MCP_CLIENT_NAME": "Claude Desktop (Client A)"
}
},
"pushengage-client-b": {
"command": "npx",
"args": ["-y", "@pushengage/mcp"],
"env": {
"PE_MCP_CONFIG_PATH": "/Users/you/.pushengage/mcp-client-b.json",
"PE_MCP_CLIENT_NAME": "Claude Desktop (Client B)"
}
}
}
}Ask the assistant to log in under each server name separately; each authorizes against whichever PushEngage account you choose in the browser.
Security and token storage
Login is browser-based. The assistant never sees your PushEngage password.
The dashboard sends the token to the server as a POST request, so it never appears in a URL, browser history, or access log.
The token is stored at
~/.pushengage/mcp.jsonwith0600permissions (readable only by you). Its expiry is set by PushEngage and is shown bypushengage_auth_status.To revoke it, run
pushengage_auth_logoutor log out of all sessions in PushEngage under Settings → Security.
Troubleshooting
The server won't connect at all ("Connection closed")
If npx -y @pushengage/mcp runs fine when you type it directly in a terminal, but your client (Claude Desktop, Cursor, etc.) shows the server as disconnected or logs something like MCP error -32000: Connection closed, this is almost always a PATH problem, not a bug in the server.
These clients are launched from your Dock/Finder, not from a terminal, so they never load your shell's startup files (.zshrc, .zprofile, etc). If Node was installed via a version manager (nvm, fnm, volta, ...), those tools only add node/npx to PATH from inside those startup files — so the client can't find npx at all, the server process never starts, and you get a generic connection error instead of a clear "command not found."
Fix: point the client at the absolute path to npx (this skips the PATH lookup for finding it) and also pass that same folder as PATH in env (so npx's own #!/usr/bin/env node shebang can find node when it re-execs). Run which npx in your terminal to get the path, then use it in your client's config:
{
"mcpServers": {
"pushengage": {
"command": "/absolute/path/from/which-npx",
"args": ["-y", "@pushengage/mcp"],
"env": {
"PATH": "/absolute/folder/containing/that/npx:/usr/bin:/bin:/usr/sbin:/sbin"
}
}
}
}Restart the client after editing. If which npx instead prints something under /usr/local/bin or /opt/homebrew/bin, your Node install isn't version-manager-based and this likely isn't your issue — check the client's own MCP logs for the actual error instead.
Other errors
AUTH_EXPIRED— your token expired. Ask the assistant to log you in again.NO_SITE_SELECTED— callpushengage_list_sitesand then ask to use one of the returned sites before using a site-scoped tool.Browser doesn't open — this happens in headless or remote (e.g. SSH) sessions. The authorize URL is printed to the terminal running the server; open it manually.
Something else — every error the server returns starts with a
[CODE]tag and a plain-language explanation; share that with support if you need help.
License
Available Tools
28 toolspushengage_auth_loginLog in to PushEngageA
Opens a browser window to the PushEngage dashboard. After you click Authorize, an access token is stored locally and used for subsequent calls; the expiry is shown in the result. Requires a browser on the local machine. In headless or SSH environments the authorization URL is printed to the terminal so it can be opened manually.
Inputs: no named parameters. Returns: authorized, expires_at
pushengage_auth_logoutLog outADestructiveIdempotent
Revokes the current PushEngage session on the server and deletes the locally stored token. After this call, all site-scoped tools require pushengage_auth_login before they can be used again.
Inputs: no named parameters. Returns: status, server_session_revoked
pushengage_auth_statusCheck authentication and site statusARead-only
Returns the current login state: authenticated (bool), expires_at (token expiry ISO string), current_site_id, api_url, dashboard_url, and client_name. Use this to check whether pushengage_auth_login is needed before making other calls.
Inputs: no named parameters. Returns: api_url, expires_at, client_name, authenticated, +2 more
pushengage_create_attributeCreate a subscriber attributeA
Creates a new subscriber attribute on the current site. Required: name (human-readable label, e.g. "Customer Plan") and key (machine identifier, e.g. "plan"). The key must start with a letter and contain only letters, numbers, hyphens, and underscores. The created key becomes a usable value for audience-group rules with field="attributes" (the rule's key property). PushEngage caps each site at 50 attributes; the API returns 422 if the limit is exceeded.
Inputs: key (required), name (required), site_id. Returns: id, key, name, status, +2 more
pushengage_create_audience_groupCreate an audience groupA
Creates a new audience group on the current site. Required: name and filter. The filter is a subscriber-filter expression — { op: "or" (the only supported value), value: 2-D array of rule groups }. Each rule is { field, op, value?, key? }. Rules WITHIN a group are AND-ed; groups in value are OR-ed, so conditions that must all hold go in ONE group. See the inputSchema field descriptions for the supported field and op enums. Common patterns: "Mobile subscribers" → filter={ op: "or", value: [[{ field: "device", op: "in", value: ["mobile"] }]] }. "Subscribed in the last 7 days" → filter={ op: "or", value: [[{ field: "ts_created", op: "ts_elapsed_lt", value: 10080 }]] } (ts_elapsed_* is in MINUTES: 7 × 1440). "Highly engaged" (≥20 sent AND ≥2 clicks) → filter={ op: "or", value: [[{ field: "sent_count", op: "gt", value: 20 }, { field: "click_count", op: "gt", value: 2 }]] }. "Sports Fans segment on mobile" → filter={ op: "or", value: [[{ field: "segments", op: "in", value: ["Sports Fans"] }, { field: "device", op: "in", value: ["mobile"] }]] } — segment NAMES are resolved to ids automatically. Call pushengage_list_audience_filter_values before any country/state/city/device/device_type rule and pushengage_list_attributes before any attributes rule: those values are site-specific, and a guessed one saves successfully but matches nobody. Only set description and complex filters when the user explicitly describes them.
Inputs: name (required), filter (required), site_id, description. Returns: id, name, filter, view_url, +2 more
pushengage_create_segmentCreate a segmentA
Creates a new segment on the current site. Required: segment_name. Optionally pass segment_criteria with URL include and/or exclude rules to define what subscribers belong to the segment — each rule is { rule: "start" | "exact" | "contains", value: "<url>" }. By default, segment criteria are evaluated only when a visitor subscribes to push notifications. Set add_segment_on_page_load=true (Segment on Page Visit) to evaluate those criteria on every page visit instead, so segment membership can change as subscribers browse the site. Only include segment_criteria and add_segment_on_page_load when the user explicitly describes the matching rules.
Inputs: segment_name (required), site_id, segment_criteria, add_segment_on_page_load. Returns: view_url, segment_id, segment_name, segment_criteria, +1 more
pushengage_get_analytics_summaryGet all-time analytics totalsARead-only
Returns the current site's all-time, site-wide totals: subscribers (current active count), notifications sent, views, clicks, and goal conversions/value. Not bounded by any date range — for trends over a period use pushengage_get_analytics_timeseries instead.
Inputs: site_id. Returns: total_views, total_clicks, total_goal_count, total_goal_value, +2 more
pushengage_get_analytics_timeseriesGet analytics over a date rangeARead-only
Returns a time series of the current site's analytics between start_date and end_date, bucketed by group_by. Each point has subscribers gained, notifications sent, views, clicks, ctr, and unsubscribes for that bucket. Use this for trends or metrics over a period; for all-time totals use pushengage_get_analytics_summary instead.
Inputs: end_date (required), start_date (required), site_id, group_by. Returns: count, points, end_date, group_by, +1 more
pushengage_get_campaign_defaultsGet campaign defaultsARead-only
Returns the current site's campaign default settings: utm_parameters (enabled + source/medium/campaign/term/content), fallback_notification (title/message/url), fallback_attributes (city/country), and default_expiry (broken into total_seconds + days/hours/minutes). These are the defaults applied to push campaigns, matching the dashboard's Campaign Defaults page.
Inputs: site_id. Returns: default_expiry, utm_parameters, fallback_attributes, fallback_notification
pushengage_get_service_worker_settingsGet service worker settingsARead-only
Returns the current site's Service Worker Settings (from the Advanced Settings page), using the dashboard labels: enable_service_worker_registration ("Enable the service worker registration from PushEngage"), enable_service_worker_in_subfolder ("Enable addition of service worker in another sub-folder"), and service_worker_file_path ("Path for service worker file").
Inputs: site_id. Returns: service_worker_file_path, enable_service_worker_in_subfolder, enable_service_wo…
pushengage_get_site_detailsGet site detailsARead-only
Returns the current site's details, matching the dashboard's Site Details page: name, URL, image, timezone, geolocation toggle, and the "Powered By PushEngage" branding toggle.
Inputs: site_id. Returns: site_id, site_url, timezone, site_name, +3 more
pushengage_list_attributesList subscriber attributesARead-only
Lists subscriber attributes (custom keys set on subscribers via the JS SDK) on the current site, paginated (response includes has_more). Use this to discover attribute key values before constructing an audience-group filter rule with field="attributes".
Inputs: page, limit, site_id, key_contains. Returns: page, limit, total, has_more, +2 more
pushengage_list_audience_filter_valuesList values for custom-audience filter fieldsARead-only
Lists the location and device values recorded on this site, with how many active subscribers carry each one. These are the values a subscriber_filter rule can use for the country, state, city, device and device_type fields — the "Custom Audience" targeting on the send tools and pushengage_create_audience_group. Call this BEFORE writing a rule on any of those five fields. Locations are display names taken from the subscribers themselves, not ISO codes, and they differ per site — "US", "USA" and "United States" are not interchangeable, and a guessed spelling produces a notification that saves successfully and reaches the wrong people. The subscriber counts also show whether a filter is worth sending at all. For the other two filter vocabularies use pushengage_list_segments (segment names) and pushengage_list_attributes (attribute keys).
Inputs: limit, fields, site_id, value_contains. Returns: fields
pushengage_list_audience_groupsList audience groupsARead-only
Lists audience groups on the current site, paginated (response includes has_more). Use this to look up audience-group IDs when the user references a group by name; those IDs are what pushengage_send_notification / pushengage_send_ab_notification accept in their audience_groups field.
Inputs: page, limit, site_id, name_contains. Returns: page, limit, total, has_more, +2 more
pushengage_list_chat_widgetsList chat widgetsARead-only
Lists the chat widgets on the current site, paginated (response includes has_more). A chat widget is the floating button that surfaces support channels (WhatsApp, Messenger, Email, etc.) on the site. Each item carries the configured channels, target devices, business-hours restriction, and a country/page targeting summary.
Inputs: page, limit, status, site_id, +1 more. Returns: page, limit, total, has_more, +2 more
pushengage_list_drip_campaignsList drip campaignsARead-only
Lists the drip autoresponder campaigns on the current site, paginated (response includes has_more). Optionally filter by status (default "all" = every status), mirroring the dashboard filter tabs. Set include_analytics=true only when the user asks for stats/performance (it costs an extra analytics lookup per page). Each item then also carries an analytics object: sent, seen, clicked, ctr, goal_count, goal_value.
Inputs: page, limit, status, site_id, +1 more. Returns: page, limit, total, has_more, +2 more
pushengage_list_notificationsList notificationsARead-only
Lists push notifications on the current site, newest first, paginated (response includes has_more). Use this to discover notification IDs and review past or upcoming sends. Set include_analytics=true only when the user asks for stats — it costs an extra lookup and adds rolled-up counts and goal conversions to each row. Each item carries content, status, targeting criteria, and delivery stats; the criteria.audience_groups ids are reusable as the send tools' audience_groups input, and absent criteria means the notification went to all subscribers.
Inputs: page, tags, limit, status, +5 more. Returns: page, limit, total, has_more, +2 more
pushengage_list_rss_campaignsList RSS auto push campaignsARead-only
Lists the RSS auto push campaigns on the current site, paginated (response includes has_more). Each item includes the feed_url. Optionally filter by status (default "all" = every status), mirroring the dashboard filter tabs.
Inputs: page, limit, status, site_id. Returns: page, limit, total, has_more, +2 more
pushengage_list_segmentsList segmentsARead-only
Lists segments on the current site, paginated (response includes has_more). Each item carries segment_id, name, current subscriber count, status, and any URL matching criteria.
Inputs: page, limit, site_id, name_contains. Returns: page, limit, total, has_more, +2 more
pushengage_list_sitesList sitesARead-only
Lists PushEngage sites the authenticated user can access. Returns site_id, site_name, site_url, and site_status. Also returns current_site_id so the assistant can see which site is already active without calling pushengage_auth_status. When the user asks to send a notification linking to their site's homepage, use site_url as the notification's url field.
Inputs: no named parameters. Returns: sites, current_site_id
pushengage_list_triggered_campaignsList triggered campaignsARead-only
Lists the triggered campaigns (Price Drop / Inventory Alert / Cart Abandonment / etc.) on the current site, paginated (response includes has_more). Optionally filter by status (default "all" = every status), mirroring the dashboard filter tabs. Set include_analytics=true only when the user asks for stats/performance (it costs an extra analytics lookup per page). Each item then also carries an analytics object: sent, seen, clicked, ctr, goal_count, goal_value.
Inputs: page, limit, status, site_id, +1 more. Returns: page, limit, total, has_more, +2 more
pushengage_list_workflowsList workflow automationsARead-only
Lists the workflow automations on the current site, paginated (response includes has_more). Optionally filter by status (default "all" = every status), mirroring the dashboard filter tabs. Set include_analytics=true only when the user asks for stats/performance (it costs an extra analytics lookup per page). Each item then also carries an analytics object: entered, active, completed, failed (user counts), goal_count, goal_value.
Inputs: page, limit, status, site_id, +1 more. Returns: page, limit, total, has_more, +2 more
pushengage_select_siteSelect current siteAIdempotent
Sets the current site used by all site-scoped tools (pushengage_send_notification, pushengage_list_segments, pushengage_get_analytics_summary, pushengage_list_drip_campaigns, etc.) when no site_id is provided. Persists across MCP restarts. Call pushengage_list_sites first to get a valid site_id.
Inputs: site_id (required). Returns: site_url, site_name, current_site_id
pushengage_send_ab_notificationSend an A/B push notificationA
Creates an A/B notification on the current site with two variants (variant_a and variant_b). Required: variant_a (title, message, url) and variant_b (title, message, url). By default (intelligent_ab_test omitted) both variants ship as-is to the audience — no automatic winner picking. Pass intelligent_ab_test to enable intelligent / auto-winner mode: each variant is sent to sent_limit_percentage% of subscribers, and after winner_delay_minutes the higher-CTR variant is automatically delivered to the remaining audience (up to sent_limit total). Only include intelligent_ab_test when the user explicitly asks for an intelligent / auto-winner test. Do not add other optional fields (tags, audience_groups, per-variant image_url, utm_params, actions, etc.) unless the user explicitly asks. Audience (pick AT MOST one — mutually exclusive; omit both to send to all subscribers): audience_groups (1-20 predefined audience-group IDs), or subscriber_filter for "Send to Custom Audience". Both apply to both variants, and subscriber_filter behaves exactly as it does on pushengage_send_notification. Use status="schedule" with schedule_date to schedule for later, or status="draft" to save without sending.
Inputs: variant_a (required), variant_b (required), tags, status, +6 more. Returns: status, view_url, notification_id, ab_notification_id, +1 more
pushengage_send_notificationSend a push notificationA
Creates and sends a push notification on the current site. Required fields: title, message, url. Do not add optional fields (tags, image_url, utm_params, audience_groups, actions, etc.) unless the user explicitly asks for them — for example, do not infer tags from the notification topic. Delivery modes (mutually exclusive — pick AT MOST one): (a) status="schedule" + schedule_date for a one-shot scheduled send; (b) pass recurring_schedule { days, times, start_date, end_date } for a recurring/repeating notification — leave status at "sent" (default) to activate the recurrence, or use "draft" to save without activating; (c) when scheduling one-shot, optionally pass send_in_subscribers_timezone=true to deliver at the scheduled wall-clock time in each subscriber's local timezone (only when the user explicitly asks, e.g. "send at 9am in their timezone"). Otherwise the notification is sent immediately. Use status="draft" to save without sending or activating. Audience — the three options the dashboard offers, pick AT MOST one (they are mutually exclusive): omit both fields for "Send to All Subscribers"; pass audience_groups (1-20 predefined audience-group IDs) for "Send to Audience Group" when the user names a saved group; or pass subscriber_filter for "Send to Custom Audience" — targeting by segment, attribute, location, device, browser, subscription or engagement date, or sent/view/click counts. Segment names in subscriber_filter are resolved automatically, so "send to my Sports Fans segment" needs no lookup — but call pushengage_list_audience_filter_values first for any country/state/city/device/device_type value, and pushengage_list_attributes first for any attribute key, because those are site-specific and a guessed value produces a notification that saves successfully and reaches the wrong people. When the user asks to use the site URL, call pushengage_list_sites and use the current site's site_url.
Inputs: url (required), title (required), message (required), tags, +15 more. Returns: url, title, status, message, +3 more
pushengage_update_campaign_defaultsUpdate campaign defaultsAIdempotent
Updates one or more of the current site's campaign default settings. Pass only the groups and fields you want to change: utm_parameters, fallback_notification, fallback_attributes, and/or default_expiry. The tool reads the current values and merges your changes, so partial edits are fine (e.g. change just utm_parameters.source, or set default_expiry to {days:7}). default_expiry is given as days/hours/minutes (omitted components count as 0; total must be between 1 minute and 28 days). When utm_parameters.enabled is true, source/medium/campaign must be non-empty after the merge. Provide at least one group. Returns the updated settings.
Inputs: site_id, default_expiry, utm_parameters, fallback_attributes, +1 more. Returns: default_expiry, utm_parameters, fallback_attributes, fallback_notification
pushengage_update_service_worker_settingsUpdate service worker settingsAIdempotent
Updates the current site's Service Worker Settings. Pass only the fields you want to change: enable_service_worker_registration, enable_service_worker_in_subfolder, and/or service_worker_file_path. The tool reads the current values and merges your changes. When enable_service_worker_registration is true, service_worker_file_path must be non-empty after the merge. Provide at least one field. Returns the updated settings.
Inputs: site_id, service_worker_file_path, enable_service_worker_in_subfolder, enable_service_worker_registration. Returns: service_worker_file_path, enable_service_worker_in_subfolder, enable_service_wo…
pushengage_update_site_detailsUpdate site detailsAIdempotent
Updates the current site's details. Pass only the fields you want to change: site_name (Site Name), site_url (Site URL), timezone (Website Time Zone, an IANA name), enable_geolocation (Enable Geolocation), and/or remove_powered_by_pushengage (Remove "Powered By PushEngage", which needs a paid plan). Provide at least one field. Returns the updated site details.
Inputs: site_id, site_url, timezone, site_name, +2 more. Returns: site_id, site_url, timezone, site_name, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Most tools target a distinct resource and action (auth_*, site settings, segments, attributes, audience groups, notifications, and five separate campaign list types), and descriptions explicitly cross-reference siblings. The only friction is the cluster of four audience-related list tools (list_segments, list_audience_groups, list_audience_filter_values, list_attributes) plus summary vs timeseries analytics, which require reading descriptions to pick correctly but are documented well enough to avoid misselection.
Every tool uses the same pushengage_ prefix followed by a consistent verb_noun snake_case pattern (auth_login, list_sites, select_site, get_site_details, update_campaign_defaults, send_ab_notification). Even the irregular 'select_site' and 'auth_*' fit the same scheme, so the naming is fully predictable.
28 tools is heavy for the rubric's comfort band, but the surface reflects a genuinely broad platform (auth, sites, three settings pages, three audience-targeting vocabularies, notifications, A/B sends, and five campaign types). The five parallel list_*_campaigns tools plus chat widgets push it past 25 without any tool being truly redundant, so it sits at borderline rather than mismatched.
Settings and site management have full get/update pairs, and sending, targeting, segments, attributes, and audience groups all support lookup and creation. However, the campaign surface is read-only (list_drip/triggered/rss/workflows with no create/update), chat widgets are list-only, and there is no delete anywhere for segments, attributes, audience groups, or notifications, leaving agents unable to complete lifecycle operations the domain implies.
Maintenance
Related MCP Connectors
Send, search, and manage notifications, accounts, and push preferences
Read Enginemailer subscribers, lists and campaigns; add subscribers, create and send campaigns.
Manage Encharge people, tags, segments and fields, and track events for email automation.
Query people, segments, campaigns, and message deliveries; send transactional email or broadcasts.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage OneSignal push notifications, email, SMS, and user management through natural language. Supports multi-channel messaging, segmentation, templates, analytics, and iOS Live Activities with 50+ tools for complete OneSignal API coverage.1-
- FlicenseBqualityCmaintenanceEnables programmatic Reddit growth campaign management via the Engain API, including task scheduling, upvote/downvote orders, opportunity discovery, and account management.29-
- AlicenseNot gradedqualityBmaintenanceDraft, test, and send Mailchimp campaigns from an MCP client with audience management, subscriber CRUD, and post-send analytics behind safe-by-default send gates.318 npm2Apache 2.0
- AlicenseAqualityBmaintenanceOfficial MCP server for PushNotif.biz.id. Enables AI agents to register websites, generate one-line SDK snippets, and broadcast or schedule Web Push (VAPID), Android FCM, iOS APNs, In-App Popups, Live Activity Toasts, and automated RSS push notifications with real-time CTR analytics.16MIT