pushengage-mcp

Manage yourPushEngageaccount from any AI assistant, in plain language.

This package is aModel 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.

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

- APushEngageaccount (free or paid) with at least one site.
- Node.js 18 or newer (the assistant runs the server vianpx).
- An MCP-capable client (Claude Desktop, Claude Code, Cursor, or any other).

The easiest path on Claude Desktop is the MCP Bundle:
- Download the latestpushengage-mcp-<version>.mcpbfile from theGitHub releases page.
- Open it with Claude Desktop (double-click it, or drag it onto the window) and clickInstall.

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

Restart Claude Desktop. The "pushengage" server should appear in your tool list.

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

Any client that speaks MCP over stdio works. Configure it to run the commandnpx -y @pushengage/mcp.

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.
- ClickAuthorize. 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 explicitsite_id. When the token expires you will see anAUTH_EXPIREDmessage; just ask to log in again.

All site-scoped tools default to the current site.

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:

Running multiple PushEngage accounts side by side

Register the server under two different names, each with its ownPE_MCP_CONFIG_PATHso 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.

- 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, runpushengage_auth_logoutor log out of all sessions in PushEngage under Settings → Security.

The server won't connect at all ("Connection closed")

Ifnpx -y @pushengage/mcpruns fine when you type it directly in a terminal, but your client (Claude Desktop, Cursor, etc.) shows the server as disconnected or logs something likeMCP error -32000: Connection closed, this is almost always aPATHproblem, 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 addnode/npxtoPATHfrom inside those startup files — so the client can't findnpxat 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 tonpx(this skips thePATHlookup for finding it) and also pass that same folder asPATHinenv(sonpx's own#!/usr/bin/env nodeshebang can findnodewhen it re-execs). Runwhich npxin 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. Ifwhich npxinstead prints something under/usr/local/binor/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.

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

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Launch & manage your User Referral and Partner / Affiliate program — for developers and growth teams.

Let AI clients add payments to your website. Create checkout pages, events and forms and embed them on your site in minutes.

Answers questions on AEO, SEO, web development and branding from the published material of GOJI, a Melbourne digital agency, with a goji.agency URL to cite on every result.

A shared campaign canvas for you and your AI agent: briefed by your brand rules, gated by your approval.

Technical SEO audits and crawl insights for AI assistants via MCP.

Run your Linkedin account from claude or chatgpt

AI agents that manage paid ads across Meta, LinkedIn, and Google Ads: campaigns, ad creative, and day-to-day ad operations from any MCP client.

Chat with any brand's Meta (Facebook/Instagram) ads inside Claude — research a competitor's ad library, surface their longest-running winners, extract hooks/formats, and clone winning ads for your own brand.