PushEngage — Claude Code MCP server: setup
Connect an AI assistant to PushEngage to send notifications, shape audiences, and inspect campaign analytics from chat.
claude mcp add --env PE_MCP_CONFIG_PATH=<PE_MCP_CONFIG_PATH> --env PE_MCP_CLIENT_NAME=<PE_MCP_CLIENT_NAME> --transport stdio pushengage -- npx -y @pushengage/mcpWhat PushEngage does
PushEngage connects an MCP-capable assistant to a PushEngage account. From the chat, you can send or schedule push notifications, run A/B tests, create segments and audience groups, review campaign metrics, and change site settings.
Sign-in happens in a browser, then the access token is stored locally. The assistant works with the selected PushEngage site, and that choice survives restarts. You need a PushEngage account with at least one site, an MCP client, and Node.js version 18 or later. The server will not start on an older Node.js release.
What it helps with
- send push notifications to subscribers
- schedule recurring campaigns
- segment visitors by URL rules and attributes
- compare notification headlines with an A/B test
- inspect campaign delivery and click metrics
Example prompts for the agent
- Sign in to PushEngage in the browser and list the sites I can access.
- Create a segment for visitors who opened
/pricing. - Show active campaigns with their sent, seen, and clicked metrics.
How to install PushEngage
Platform CLI
claude mcp add --env PE_MCP_CONFIG_PATH=<PE_MCP_CONFIG_PATH> --env PE_MCP_CLIENT_NAME=<PE_MCP_CLIENT_NAME> --transport stdio pushengage -- npx -y @pushengage/mcpReplace <…> with your own values
Platform CLI
codex mcp add pushengage --env PE_MCP_CONFIG_PATH=<PE_MCP_CONFIG_PATH> --env PE_MCP_CLIENT_NAME=<PE_MCP_CLIENT_NAME> -- npx -y @pushengage/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"pushengage": {
"command": "npx",
"args": [
"-y",
"@pushengage/mcp"
],
"env": {
"PE_MCP_CONFIG_PATH": "<PE_MCP_CONFIG_PATH>",
"PE_MCP_CLIENT_NAME": "<PE_MCP_CLIENT_NAME>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"pushengage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pushengage/mcp"
],
"env": {
"PE_MCP_CONFIG_PATH": "<PE_MCP_CONFIG_PATH>",
"PE_MCP_CLIENT_NAME": "<PE_MCP_CLIENT_NAME>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e PE_MCP_CONFIG_PATH=<PE_MCP_CONFIG_PATH> -e PE_MCP_CLIENT_NAME=<PE_MCP_CLIENT_NAME> pushengage npx -y @pushengage/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about PushEngage
How do I install PushEngage in Claude Code?
Run claude mcp add pushengage-mcp -- npx -y @pushengage/mcp.
What does PushEngage do?
It lets an assistant manage PushEngage from chat: send notifications, build audiences, run A/B tests, and inspect campaign analytics.
What does PushEngage require?
You need a PushEngage account with at least one site, an MCP client, and Node.js version 18 or later. The first sign-in takes place in a browser.
