Notice: There is no legacy documentation available for this item, so you are seeing the current documentation.
The PushEngage MCP server lets you run your push notification stack from an AI chat window. You connect the server to an AI client such as Claude, approve access once in your browser, and then manage sites, subscribers, audiences, campaigns, and analytics by describing what you want in plain language. This guide walks through connecting the server and everything you can do with it, with a short video for each step.
Before You Start
- You need a PushEngage account and at least one active site.
- You need an AI client that supports MCP, such as Claude. The server is published as
@pushengage/mcpand exposes 27 tools. - Approval happens in your browser, never in the chat. When a client first connects, PushEngage opens a browser window where you authorize access, and you can revoke it at any time from My Account » Active Sessions.
- The access token is issued to the local client on your device and is time limited.
How the MCP Server Works
You talk to PushEngage in the chat window, and the server turns your request into the right action on your account. Each request maps to one of the server’s tools, and actions that send or change data are confirmed before they run. Your selected site stays active across the session, so you set it once and keep working.
| Area | What you can do |
|---|---|
| Account and session | Log in, check your login status, and log out. |
| Sites | List your sites, select the active site, and view or update site settings. |
| Subscribers and audiences | List and create custom attributes, segments, and audience groups. |
| Sending | Send a push notification, send an A/B notification, and list sent notifications. |
| Campaigns and automations | View drip campaigns, triggered campaigns, workflows, RSS campaigns, chat widgets, and campaign defaults. |
| Analytics | Get a lifetime analytics summary and analytics over time. |
Connect and Log In
Add the PushEngage MCP server to your AI client, then ask it to log you in. The client opens a browser window where you click Authorize to grant access. Once you approve, the chat confirms you are logged in and shows when the session expires.
- Add the
@pushengage/mcpserver to your AI client. [Confirm: exact install command or config per client, such as Claude, Cursor, and VS Code.] - Ask the assistant to log you in, for example,
log me in to pushengage. - In the browser window that opens, review the access request and click Authorize.
- Return to the chat, where you see your login confirmed and the session expiry.
Choose Your Site
If you manage more than one site, ask for your sites and then select the one you want to work on. The selected site stays active for the rest of the session, so later requests apply to it automatically.
- Ask for your sites, for example,
show my PushEngage sites. - Note the Site ID of the site you want.
- Ask the assistant to use that site, for example,
use site Playground.
Manage Subscribers, Attributes, and Audiences
Describe the subscriber data you want and the assistant creates it. You can list and create custom attributes, create segments, and build audience groups from a plain-language description.
Custom attributes
Ask for your custom attributes, or create a new one by describing it, for example, create an attribute called Customer Plan with key plan. The assistant confirms the attribute with its ID, name, key, and status.
Segments and audience groups
Create a segment by describing the visitors it should capture, and list or build audience groups the same way. For example, create an audience of gold-plan mobile customers in the US returns a new audience group with its filter logic and an ID you can reuse when sending.
Send, Confirm, and Schedule
Ask the assistant to send a notification and it shows you exactly what will go out before anything sends. Push notifications go out immediately and cannot be recalled, so the assistant always asks you to confirm first.
- Describe the notification, for example,
send a notification titled 'Sale ends tonight', message 'Last call, 50 percent off', linking to https://example.com/sale. - Review the preview the assistant shows you.
- Reply to confirm, and the assistant sends it and returns the notification ID.
To schedule instead of sending now, say when, for example, schedule one for 9 AM in each subscriber's local timezone. The assistant schedules a send that reaches each subscriber at their own local time.
A/B Test Notifications
Ask for an A/B test to compare two versions and let PushEngage roll out the winner automatically. You set the test size, the winning metric, and the delay before the winner goes to the rest of your audience.
For example, run an A/B test of two headlines and auto-roll-out the winner by click rate after 60 minutes, capped at 10,000 subscribers with 10 percent per variant. The assistant sets up the test and schedules the automatic winner rollout.
Manage Campaigns, Workflows, and Defaults
Ask for the status of your automations and change account defaults in a single line. You can list drip campaigns, triggered campaigns, workflows with their entered, completed, and failed counts, chat widgets, and RSS campaigns.
To change a default, describe it, for example, set my default notification expiry to 7 days. The assistant applies the change and confirms the previous value. You can also check your campaign defaults, such as whether UTM parameters are enabled.
Site Settings
Ask the assistant to review or update site settings such as the service worker location, site timezone, and geolocation. If a setting already matches what you asked for, the assistant tells you there is nothing to change instead of making a redundant update.
Review Analytics
Ask for your numbers and the assistant returns them in the chat. You can list your sent notifications with their views and clicks, see your best performer, and get a lifetime analytics summary for the site.
For example, give me the lifetime analytics summary for this site returns a table of active subscribers, notifications sent, views, clicks, and goal conversions, along with a quick read of your click-through rate.
Frequently Asked Questions
Where do I approve access, and is it safe?
You approve access in your browser, never in the chat. The access token is issued to the local client on your device and is time limited, and you can revoke it at any time from My Account » Active Sessions. Because approval happens through the browser, your assistant never handles your password.
Which AI clients work with the PushEngage MCP server?
Any client that supports MCP can connect to @pushengage/mcp. [Confirm: the official list of supported and tested clients, such as Claude, Cursor, and VS Code, plus the exact setup steps for each.]
Do I have to select my site every time?
No. Once you select a site, it stays active for the rest of your session, so later requests apply to that site until you switch. If you manage one site, the assistant works with it directly.
Will the assistant send a notification without asking me?
No. Sends and other changes are confirmed before they run. Because push notifications go out immediately and cannot be recalled, the assistant shows you exactly what will send and waits for your confirmation.
What can the MCP server actually do?
It exposes 27 tools covering account and session, sites and site settings, subscriber attributes, segments and audience groups, sending and A/B testing, campaigns and workflows, campaign defaults, and analytics. See the capability table earlier in this guide for the full breakdown.
If you run into any issues, please feel free to contact us by clicking here. Our support team will be able to help you.
