Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

PushEngage

by awesomemotiveversion 1.2.0i★ 8iRuns on your computerOfficial site ↗
Registry nameio.github.awesomemotive/pushengage-mcp

How to install

What it does

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

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Marketing & social media

Use together with

Skills that teach the AI this kind of work; they work alongside this one

scroll-world

A skill that turn any brand into a scrollable 3D world landing page

by oso95★ 11,0651 skills

Skill · How-to guide

social-auto-upload

自动化上传视频到社交媒体:抖音、小红书、视频号、tiktok、youtube、bilibili

by dreammis★ 16,698 (whole repo)4 skills

Skill · How-to guide

native-subtitle-quote-image

保留视频内嵌字幕,精确取帧并生成 3:4 社交长图的 Agent Skill

by chengyi-ai★ 2,8911 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity11/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score23/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install PushEngage. Follow https://mcp.popnx.com/i/awesomemotive-pushengage-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server PushEngage for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "pushengage": { "command": "npx", "args": [ "-y", "@pushengage/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the PushEngage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "pushengage": {
          "command": "npx",
          "args": [
            "-y",
            "@pushengage/mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use PushEngage and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using PushEngage or shows a PushEngage tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PE_MCP_CONFIG_PATH Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side.
  • PE_MCP_CLIENT_NAME Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop".

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect PushEngage yet

PushEngage runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect PushEngage

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Marketing & social media that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server PushEngage for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user pushengage -- npx -y @pushengage/mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the PushEngage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user pushengage -- npx -y @pushengage/mcp
  4. Type /mcp in Claude Code

    You should see PushEngage listed as connected

  5. Try it

    Use PushEngage and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using PushEngage or shows a PushEngage tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PE_MCP_CONFIG_PATH Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side.
  • PE_MCP_CLIENT_NAME Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop".

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server PushEngage for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "pushengage": { "command": "npx", "args": [ "-y", "@pushengage/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the PushEngage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use PushEngage and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using PushEngage or shows a PushEngage tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PE_MCP_CONFIG_PATH Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side.
  • PE_MCP_CLIENT_NAME Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop".

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server PushEngage for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "pushengage": { "type": "stdio", "command": "npx", "args": [ "-y", "@pushengage/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the PushEngage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use PushEngage and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using PushEngage or shows a PushEngage tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PE_MCP_CONFIG_PATH Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side.
  • PE_MCP_CLIENT_NAME Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop".

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use PushEngage💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user pushengage -- npx -y @pushengage/mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "pushengage": {
      "command": "npx",
      "args": [
        "-y",
        "@pushengage/mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "pushengage": {
      "command": "npx",
      "args": [
        "-y",
        "@pushengage/mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "pushengage": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pushengage/mcp"
      ]
    }
  }
}

Values you fill in

  • PE_MCP_CONFIG_PATH env
    Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side.
  • PE_MCP_CLIENT_NAME env
    Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop".

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
113/wk
Connection
Runs on your computer
Latest versioni
1.2.0
Published to registryi
Nov 18, 2026
Code last changedi
Nov 18, 2026
Maker
awesomemotive
Packages
npm: @pushengage/mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account awesomemotive, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/awesomemotive-pushengage-mcp.svg)](https://mcp.popnx.com/en/servers/awesomemotive-pushengage-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Marketing & social mediai

  • More stars than 96% of the other 4225 servers in this category
  • Published to the registry more recently than 96% of the other 4225 servers in this category
  • Basic checks equal to or better than 99% of the other 4225 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PushEngage safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 days ago, and the latest version (1.2.0) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

by ChatbotXIOGrowing★ 1.1K Stars for the whole repoUpdated 14 days ago

Runs in the cloud✓ service owner · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

by betterlyticsGrowing★ 196Updated 4 months ago

Runs in the cloud✓ service owner · betterlytics.io
Compared with similar ones
This one
PushEngage
RelaticleChatbotXX (Twitter) MCP Server by XquikBetterlyticsBibiGPT YouTube Video Summarizer
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoYesNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/44/44/4
LicenseMITAGPL-3.0NOASSERTIONMITAGPL-3.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

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

  1. Ask: "Log me into PushEngage." The server opens a browser tab to the PushEngage authorize page.
  2. Click Authorize. The tab confirms success and an access token is saved locally.
  3. 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
ToolPurpose
pushengage_auth_loginOpens the browser to PushEngage and stores the token on success.
pushengage_auth_statusShows whether you are authenticated and which site is selected.
pushengage_auth_logoutDeletes the locally stored token.
pushengage_list_sitesLists the PushEngage sites you can access.
pushengage_select_siteSets the current site used by the other tools.
Site settings
ToolPurpose
pushengage_get_site_details / pushengage_update_site_detailsSite name, URL, timezone, geolocation, and the "Powered By PushEngage" branding toggle.
pushengage_get_campaign_defaults / pushengage_update_campaign_defaultsUTM parameters, fallback notification, fallback attributes, and default notification expiry. Updates merge over current values, so partial edits work.
pushengage_get_service_worker_settings / pushengage_update_service_worker_settingsService worker registration, sub-folder support, and the worker file path.
Audiences
ToolPurpose
pushengage_list_segments / pushengage_create_segmentURL-rule based subscriber segments.
pushengage_list_audience_groups / pushengage_create_audience_groupSaved targeting groups (device, country, segment, engagement, dates, attributes). Referenced by the send tools' audience_groups.
pushengage_list_attributes / pushengage_create_attributeCustom subscriber attribute keys used in audience-group rules (max 50 per site).
pushengage_list_audience_filter_valuesThe location and device values recorded on this site, with subscriber counts — the values a Custom Audience filter rule can use for country / state / city / device / device_type. Call before writing one of those rules: locations are site-specific display names, not ISO codes.
Campaigns and automations
ToolPurpose
pushengage_list_drip_campaignsDrip autoresponders. Filter by status; set include_analytics for per-campaign stats.
pushengage_list_triggered_campaignsTriggered campaigns (cart/browse abandonment, price drop, etc.). Filter by status; optional analytics.
pushengage_list_rss_campaignsRSS auto push campaigns. Filter by status.
pushengage_list_workflowsWorkflow automations. Filter by status; set include_analytics for entered/active/completed/failed and goal stats.
Chat widgets
ToolPurpose
pushengage_list_chat_widgetsThe on-site widget that surfaces WhatsApp, Messenger, and other channels. Shows status, channels, devices, business-hours restriction, and targeting.
Analytics
ToolPurpose
pushengage_get_analytics_summaryLifetime totals: subscribers, notifications sent, views, clicks, and goal count/value.
pushengage_get_analytics_timeseriesPer-bucket (day/week/month) subscribers, sends, views, clicks, CTR, and unsubscribes over a date range.
Sending notifications
ToolPurpose
pushengage_list_notificationsLists sent, scheduled, and draft notifications, newest first. Filter by status (dashboard-tab semantics), sent-date range, or tags; set include_analytics for rolled-up A/B and timezone-send stats.
pushengage_send_notificationSends or schedules a notification. One tool, three delivery modes: send now, one-shot schedule (optionally per-subscriber timezone), and recurring. schedule_timezone lets you give the time in your own IANA timezone and have it converted to the site's, with both wall clocks reported back. Targeting mirrors the dashboard's three options: omit both fields for All Subscribers, audience_groups for an Audience Group, or subscriber_filter for a Custom Audience (segments, location, device, attributes, engagement — segment names are resolved to IDs and verified before sending).
pushengage_send_ab_notificationAn A/B notification with two variants. Pass intelligent_ab_test to sample each variant, pick the winner by click rate after a delay, and roll the winner out to the rest. Supports the same audience_groups / subscriber_filter targeting, applied to both variants.

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 varDefaultPurpose
PE_MCP_CLIENT_NAMEAI assistantLabel shown on the authorize screen as the requesting app. Set it if you want a specific label, e.g. "Claude Desktop".
PE_MCP_CONFIG_PATH~/.pushengage/mcp.jsonWhere 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 ~ expansion.
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.json with 0600 permissions (readable only by you). Its expiry is set by PushEngage and is shown by pushengage_auth_status.
  • To revoke it, run pushengage_auth_logout or 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": { "

Only the beginning is shown; read the rest in the repo