MCP.Market

PushEngage MCP server

by awesomemotive·io.github.awesomemotive/pushengage-mcp·v1.0.0·8 stars
No reviews yet

Send push notifications, build audiences, and view campaign analytics from PushEngage.

A89/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

8 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed PushEngage yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PushEngage tools (27, 8 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • pushengage_auth_login

    Opens a browser window to the PushEngage dashboard. After you click Authorize, an access

  • pushengage_auth_logout

    Revokes the current PushEngage session on the server and deletes the locally stored token.

  • pushengage_auth_status

    Returns the current login state: authenticated (bool), expires_at (token expiry ISO

  • pushengage_create_attributewrite action

    Creates a new subscriber attribute on the current site. Required: `name` (human-readable label, e.g.

  • pushengage_create_audience_groupwrite action

    Creates a new audience group on the current site. Required: `name` and `filter`. The `filter` is a

  • pushengage_create_segmentwrite action

    Creates a new segment on the current site. Required: segment_name.

  • pushengage_get_analytics_summary

    Returns the current site's all-time, site-wide totals: subscribers (current active

  • pushengage_get_analytics_timeseries

    Returns a time series of the current site's analytics between start_date and end_date,

  • pushengage_get_campaign_defaults

    Returns the current site's campaign default settings: utm_parameters (enabled +

  • pushengage_get_service_worker_settings

    Returns the current site's Service Worker Settings (from the Advanced Settings page), using

  • pushengage_get_site_details

    Returns the current site's details, matching the dashboard's Site Details page: name,

  • pushengage_list_attributes

    Lists subscriber attributes (custom keys set on subscribers via the JS SDK) on the current

  • pushengage_list_audience_groups

    Lists audience groups on the current site, paginated (response includes `has_more`).

  • pushengage_list_chat_widgets

    Lists the chat widgets on the current site, paginated (response includes `has_more`). A

  • pushengage_list_drip_campaigns

    Lists the drip autoresponder campaigns on the current site, paginated (response includes

  • pushengage_list_notifications

    Lists push notifications on the current site, newest first, paginated (response includes

  • pushengage_list_rss_campaigns

    Lists the RSS auto push campaigns on the current site, paginated (response includes

  • pushengage_list_segments

    Lists segments on the current site, paginated (response includes `has_more`). Each item

  • pushengage_list_sites

    Lists PushEngage sites the authenticated user can access. Returns site_id, site_name,

  • pushengage_list_triggered_campaigns

    Lists the triggered campaigns (Price Drop / Inventory Alert / Cart Abandonment / etc.) on

  • pushengage_list_workflows

    Lists the workflow automations on the current site, paginated (response includes

  • pushengage_select_site

    Sets the current site used by all site-scoped tools (pushengage_send_notification,

  • pushengage_send_ab_notificationwrite action

    Creates an A/B notification on the current site with two variants (variant_a and variant_b).

  • pushengage_send_notificationwrite action

    Creates and sends a push notification on the current site. Required fields: title, message, url.

  • pushengage_update_campaign_defaultswrite action

    Updates one or more of the current site's campaign default settings. Pass only the groups

  • pushengage_update_service_worker_settingswrite action

    Updates the current site's Service Worker Settings. Pass only the fields you want to change:

  • pushengage_update_site_detailswrite action

    Updates the current site's details. Pass only the fields you want to change: site_name (Site

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan83 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 48 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PushEngage compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 48,255 servers
Tools
27
the typical server has 7
Tools that change things
30%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
8
more than 86% of 28,688 servers
Downloads a week
34
more than 23% of 12,191 servers with a package

What its tools let an agent do: 19 read · 8 change

Install PushEngage in Claude Code, Cursor or VS Code

Runs npx -y @pushengage/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pushengage-mcp -- npx -y @pushengage/mcp
Add to Cursor

What the publisher says

From the PushEngage repository's README, as published. We do not edit it. Read it on GitHub

@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

  • What you can do
  • Requirements
  • Install
  • First run: logging in
  • Tools
  • Configuration
  • Security and token storage
  • Troubleshooting
  • License

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 18 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:

  1. Download the latest pushengage-mcp-.mcpb file from the GitHub releases page.
  2. 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/claudedesktopconfig.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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PushEngage: common questions

Is PushEngage MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the PushEngage safety report
How do I install PushEngage?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PushEngage need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is PushEngage maintained?
The last commit was 89 days ago (2026-08-07). The latest release is v1.0.0.
How does PushEngage compare with other MCP servers?
safety score 89/100 (higher than 80% of 48,255 servers); tools 27 (the typical server has 7); tools that change things 30% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.