PushAlert
Send and manage Web Push notifications, subscriber segments, attributes, and automation for a PushAlert website project.
Verdict
Common use cases
- Broadcast product launch to all subscribers
- Notify high-value segment about flash sale
- Pull campaign CTR for weekly report
- Segment trial users by signup date
- Alert support team when critical issue resolved
Integration
- Vendor
- PushAlert
- Category
- other
- Auth
- API_KEY
- Tools
- 9
- Composio slug
push_alert
Tools
- Add Subscribers to Segment
Add one or more Web Push subscribers to an existing segment.
- Create Segment
Create a Web Push subscriber segment with a letters-and-digits name.
- Delete Segmentdestructive
Permanently delete a Web Push subscriber segment by ID.
- Get Notification Stats
Get attempted, delivered, clicked, and click-through-rate statistics for a Web Push notification.
- Get Subscriber Attributes
Get custom attributes for a Web Push subscriber.
- List Segments
List all Web Push subscriber segments and their subscriber counts.
- Remove Subscribers from Segmentdestructive
Remove one or more Web Push subscribers from an existing segment.
- Send Web Push Notification
Send an irreversible Web Push notification to a saved segment, explicit subscriber IDs, or attribute-matched subscribers. If no targeting field is supplied, sends to every subscriber. Excludes paid rich-media, audience-creator, and scheduli
- Set Subscriber Attributes
Add or update custom attributes for a Web Push subscriber.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and click 'Add MCP'. 2. Search for PushAlert and select it. 3. Log into your PushAlert dashboard, navigate to API Settings, and copy your API key. 4. Paste the key into Switchy's auth field and click 'Connect'. 5. Switchy will verify the key by listing your segments; if successful, you'll see a green checkmark. 6. Open any Project, type '@PushAlert list segments' in the chat, and press Enter. 7. The MCP will return your current segments and subscriber counts, confirming the connection works. 8. To send a test notification, create a small test segment first, then use '@PushAlert send notification to that segment with a short message'. 9. Check your PushAlert dashboard to confirm delivery stats appear within a few minutes.
What teammates see: by default, memories from PushAlert are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Send Launch Announcement
@PushAlert send a web push notification to all subscribers with the title 'New Feature Live' and message 'Check out our redesigned dashboard—log in now to explore.'
Create VIP Segment
@PushAlert create a new segment called 'VIPCustomers2024' so we can send exclusive deals to our top spenders.
Check Campaign Performance
@PushAlert get the notification stats for our last campaign—show me delivered count, clicks, and CTR so I can update the marketing deck.
Target Trial Users
@PushAlert send a notification to subscribers where the attribute 'plan' equals 'trial' with the message 'Your trial ends in 3 days—upgrade now for 20% off.'
Clean Up Old Segments
@PushAlert list all segments with their subscriber counts, then delete any segment that has zero subscribers or was created before January 2024.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@pushalert list all my subscriber segments and show me which ones have the most active users
Found 4 segments in your PushAlert account: 1. **Premium Users** – 2,847 subscribers 2. **Blog Readers** – 12,103 subscribers 3. **Cart Abandoners** – 1,592 subscribers 4. **Weekly Newsletter** – 8,764 subscribers The Blog Readers segment has the largest audience, followed by Weekly Newsletter. Premium Users and Cart Abandoners are smaller, more targeted groups. You can use these segments to send tailored notifications based on user behavior.
This example shows how the MCP retrieves segment metadata from your PushAlert account. The subscriber counts reflect your current state and update in real time. Requires read access via your API key. Useful for planning notification campaigns before you send.
@pushalert send a push notification to the Cart Abandoners segment with the title 'Your cart is waiting' and message 'Complete your order and get 10% off today'
Web Push notification sent successfully to the **Cart Abandoners** segment (1,592 subscribers). **Title:** Your cart is waiting **Message:** Complete your order and get 10% off today **Status:** Queued for delivery Notifications are irreversible once sent. You can check delivery and click-through stats in a few minutes using the notification ID returned by PushAlert.
This example demonstrates the send action, which is immediate and cannot be undone. The MCP does not validate your message content for tone or compliance—review your copy carefully. If you omit the segment parameter, the notification goes to all subscribers. Always test with a small segment first.
@pushalert get the stats for notification ID 987654 and tell me if the click-through rate suggests I should adjust my messaging strategy
**Notification ID 987654** stats: - **Attempted:** 8,764 - **Delivered:** 8,401 (95.9%) - **Clicked:** 336 (4.0% CTR) A 4% click-through rate is below the typical 5–10% benchmark for promotional Web Push. Consider testing shorter titles, more urgent language, or a clearer call-to-action. The 95.9% delivery rate is healthy, so the issue is likely engagement rather than reach.
This example pairs PushAlert's stats retrieval with the AI's interpretation. The MCP returns raw numbers; the AI applies industry context to suggest next steps. Stats are typically available 10–15 minutes after send. Requires the notification ID from a prior send action.
Use-case deep-dives
When PushAlert beats email for same-day product drops
A 6-person SaaS team ships a new dashboard feature on Tuesday morning and wants active users to see it before lunch. PushAlert wins here because web push lands in 2-3 seconds versus email's 15-minute average open window, and the team already segments users by plan tier in their app. They fire a notification to the "pro_plan" segment using Send Web Push Notification, check click-through rates with Get Notification Stats by 1pm, and see 18% engagement versus their usual 4% email open rate. The trade-off: this only works if your users opted into browser notifications during onboarding, so if fewer than 20% of actives are subscribed, email still has better reach. If you need same-day awareness and have decent opt-in rates, PushAlert closes the loop faster than any inbox.
Why PushAlert falls short for internal team notifications
A 3-person support team wants instant alerts when a ticket gets tagged "urgent" in their helpdesk, thinking web push will beat Slack noise. PushAlert isn't the right call because it's built for customer-facing browser notifications, not internal team coordination, and the 9 tools here (segment management, subscriber attributes, notification stats) assume you're messaging end-users who opted in on your public site. There's no helpdesk integration, no role-based routing, and no way to target "whoever is on-call today" without manually syncing subscriber IDs from another system. If you need sub-60-second alerts to a rotating on-call schedule, a dedicated incident tool like PagerDuty or a Slack webhook does the job with less duct tape. Save PushAlert for customer comms where you control the opt-in flow and segment logic.
When PushAlert works for low-frequency audience re-engagement
A 2-person content team publishes 3 blog posts a week and wants to re-engage the 12,000 readers who subscribed to push notifications but haven't visited in 30 days. PushAlert is a solid fit because the team can use Get Subscriber Attributes to filter by last-visit timestamp, create a "lapsed_readers" segment with Create Segment, then send a Friday digest via Send Web Push Notification with click tracking via Get Notification Stats. The workflow is simple, the API key auth takes 5 minutes to set up, and the cost is predictable per send. The boundary: if you're sending more than once a day, users unsubscribe fast and your opt-in rate craters, so this works best for weekly or bi-weekly cadences where the content is genuinely fresh. If you have a low-frequency, high-intent audience and want cheaper reach than paid social, PushAlert delivers without the email fatigue.
Frequently asked
What does the PushAlert MCP let Switchy do?
It lets AI agents send web push notifications to your subscribers, manage segments, and pull delivery stats. You can target notifications by segment, subscriber ID, or custom attributes — or broadcast to everyone. Agents can also create and delete segments, add or remove subscribers, and fetch individual subscriber attributes. It's the full PushAlert API surface, minus the paid retargeting features.
Do I need admin access to connect PushAlert?
You need a PushAlert API key, which is generated from your account dashboard. Only account owners or users with API access can create keys. The key grants full read-write access to your subscriber base and notification history, so treat it like a password. If your team uses role-based access in PushAlert, make sure the key-holder has permission to send notifications and manage segments.
Can the MCP schedule notifications or set up drip campaigns?
No. The MCP sends notifications immediately — there's no scheduling, no A/B testing, no drip sequences. If you need those, build them in PushAlert's dashboard or use a separate automation tool that calls Switchy's API on a schedule. The MCP is for real-time, agent-triggered sends: 'notify this segment when X happens', not 'send this every Tuesday'.
How is this different from using PushAlert's dashboard or API directly?
The dashboard is manual; the API requires you to write code. The MCP sits in between: AI agents decide when and what to send based on conversation context, Slack events, or data from other MCPs. You get programmable push without maintaining a cron job or webhook server. The trade-off is you lose PushAlert's visual campaign builder and scheduling UI.
Who on the team should connect this MCP?
Whoever owns your push notification strategy and has access to PushAlert's API keys. That's usually a growth or product marketer, not a developer. Once connected, any Switchy workspace member can ask agents to send notifications — so set clear team guidelines about who approves broadcast sends. The MCP doesn't enforce approval workflows; you do.