scroll-world
A skill that turn any brand into a scrollable 3D world landing page
Send push notifications, build audiences, and view campaign analytics from PushEngage.
Skills that teach the AI this kind of work; they work alongside this one
A skill that turn any brand into a scrollable 3D world landing page
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 23/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
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
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
SettingsDeveloperEdit Config
{
"mcpServers": {
"pushengage": {
"command": "npx",
"args": [
"-y",
"@pushengage/mcp"
]
}
}
}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
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
A · Use an app that can connect PushEngage
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user pushengage -- npx -y @pushengage/mcpYou should see PushEngage listed as connected
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
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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
Claude Code
claude mcp add --scope user pushengage -- npx -y @pushengage/mcpClaude 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"
]
}
}
}PE_MCP_CONFIG_PATH envPE_MCP_CLIENT_NAME envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @pushengage/mcpBased 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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account awesomemotive, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/awesomemotive-pushengage-mcp)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 2 days ago, and the latest version (1.2.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
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
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| This one PushEngage | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
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.
Once connected, just describe what you want. A few examples:
Send and schedule
Target the right people
Understand performance
Configure a site
npx).Add the server to your client's MCP config. No global install is needed; npx fetches it on demand.
The easiest path on Claude Desktop is the MCP Bundle:
pushengage-mcp- .mcpb file from the GitHub releases page.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).
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.
Edit ~/.cursor/mcp.json:
{
"mcpServers": { "pushengage": { "command": "npx", "args": ["-y", "@pushengage/mcp"] } } }
Any client that speaks MCP over stdio works. Configure it to run the command npx -y @pushengage/mcp.
Authentication is browser-based, so your credentials never touch the assistant.
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.
All site-scoped tools default to the current site.
| Tool | Purpose |
|---|---|
pushengage_auth_login | Opens the browser to PushEngage and stores the token on success. |
pushengage_auth_status | Shows whether you are authenticated and which site is selected. |
pushengage_auth_logout | Deletes the locally stored token. |
pushengage_list_sites | Lists the PushEngage sites you can access. |
pushengage_select_site | Sets the current site used by the other tools. |
| Tool | Purpose |
|---|---|
pushengage_get_site_details / pushengage_update_site_details | Site name, URL, timezone, geolocation, and the "Powered By PushEngage" branding toggle. |
pushengage_get_campaign_defaults / pushengage_update_campaign_defaults | UTM 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_settings | Service worker registration, sub-folder support, and the worker file path. |
| Tool | Purpose |
|---|---|
pushengage_list_segments / pushengage_create_segment | URL-rule based subscriber segments. |
pushengage_list_audience_groups / pushengage_create_audience_group | Saved targeting groups (device, country, segment, engagement, dates, attributes). Referenced by the send tools' audience_groups. |
pushengage_list_attributes / pushengage_create_attribute | Custom subscriber attribute keys used in audience-group rules (max 50 per site). |
pushengage_list_audience_filter_values | The 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. |
| Tool | Purpose |
|---|---|
pushengage_list_drip_campaigns | Drip autoresponders. Filter by status; set include_analytics for per-campaign stats. |
pushengage_list_triggered_campaigns | Triggered campaigns (cart/browse abandonment, price drop, etc.). Filter by status; optional analytics. |
pushengage_list_rss_campaigns | RSS auto push campaigns. Filter by status. |
pushengage_list_workflows | Workflow automations. Filter by status; set include_analytics for entered/active/completed/failed and goal stats. |
| Tool | Purpose |
|---|---|
pushengage_list_chat_widgets | The on-site widget that surfaces WhatsApp, Messenger, and other channels. Shows status, channels, devices, business-hours restriction, and targeting. |
| Tool | Purpose |
|---|---|
pushengage_get_analytics_summary | Lifetime totals: subscribers, notifications sent, views, clicks, and goal count/value. |
pushengage_get_analytics_timeseries | Per-bucket (day/week/month) subscribers, sends, views, clicks, CTR, and unsubscribes over a date range. |
| Tool | Purpose |
|---|---|
pushengage_list_notifications | Lists 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_notification | Sends 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_notification | An 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. |
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 |
|---|---|---|
PE_MCP_CLIENT_NAME | AI assistant | Label 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.json | 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 ~ expansion. |
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.
~/.pushengage/mcp.json with 0600 permissions (readable only by you). Its expiry is set by PushEngage and is shown by pushengage_auth_status.pushengage_auth_logout or log out of all sessions in PushEngage under Settings → Security.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": { "