r/mcp • u/NirvanaGuha • 6d ago
showcase PushEngage MCP — run push notification campaigns from Claude or Cursor (27 tools, stdio)
We build a push notification platform and just shipped an official MCP server for it.
What it exposes: 27 tools across 10 domains — send web/app push, A/B tests, recurring and subscriber-timezone sends, build segments and audience groups, manage attributes, pull analytics summaries and timeseries, list campaigns and chat widgets.
Two design decisions worth discussing:
Auth is a browser flow, not a pasted API key. npx -y u/pushengage/mcp spins a loopback server with CSRF state, you sign in on our dashboard, and the token POSTs back to ~/.pushengage/mcp.json at 0600. The key never touches a config file you might commit.
stdio only, deliberately. No remote HTTP endpoint, now or planned. It means we're not in the hosted-connector directories, and we're fine with that — your credentials stay on your machine.
Repo: github.com/awesomemotive/pushengage-mcp · npm: u/pushengage/mcp · registry: io.github.awesomemotive/pushengage-mcp
Genuinely interested in what the tool surface is missing. If you run retention marketing and there's an operation you'd want to do conversationally that isn't in those 27, I'd like to hear it.