Send push notifications, build audiences, and view campaign analytics from PushEngage.
Connect Runs on your machine
claude mcp add pushengage-mcp -e PE_MCP_CONFIG_PATH=<PE_MCP_CONFIG_PATH> -e PE_MCP_CLIENT_NAME=<PE_MCP_CLIENT_NAME> -- npx -y @pushengage/[email protected]{
"mcpServers": {
"pushengage-mcp": {
"command": "npx",
"args": [
"-y",
"@pushengage/[email protected]"
],
"env": {
"PE_MCP_CONFIG_PATH": "<PE_MCP_CONFIG_PATH>",
"PE_MCP_CLIENT_NAME": "<PE_MCP_CLIENT_NAME>"
}
}
}
}{
"mcpServers": {
"pushengage-mcp": {
"command": "npx",
"args": [
"-y",
"@pushengage/[email protected]"
],
"env": {
"PE_MCP_CONFIG_PATH": "<PE_MCP_CONFIG_PATH>",
"PE_MCP_CLIENT_NAME": "<PE_MCP_CLIENT_NAME>"
}
}
}
}{
"servers": {
"pushengage-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pushengage/[email protected]"
],
"env": {
"PE_MCP_CONFIG_PATH": "<PE_MCP_CONFIG_PATH>",
"PE_MCP_CLIENT_NAME": "<PE_MCP_CLIENT_NAME>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
PE_MCP_CONFIG_PATHOptional | Path to the token/config file. Defaults to ~/.pushengage/mcp.json. Set it to run multiple PushEngage accounts side by side. |
PE_MCP_CLIENT_NAMEOptional | Label shown on the PushEngage authorize screen as the requesting app, e.g. "Claude Desktop". |
Details
| Package | @pushengage/[email protected] (NPM, stdio) |
| First published | 10 Nov 2026 |
| Last updated | 10 Nov 2026 |
| Registry name | io.github.awesomemotive/pushengage-mcp |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.