Webpushr
Webpushr enables websites to send push notification campaigns to all subscribers, segments, custom audiences, or individual subscribers and monitor campaign delivery.
Verdict
Common use cases
- Announce product launches to beta segments
- Send cart abandonment reminders at scale
- Alert all users about service outages
- Re-engage dormant subscribers with offers
- Track notification open rates after campaigns
Integration
- Vendor
- Webpushr
- Category
- other
- Auth
- API_KEY
- Tools
- 6
- Composio slug
webpushr
Tools
- Get Notification Status
Get delivery and engagement counts for a Webpushr notification campaign using its campaign ID.
- Get Subscriber Count
Return lifetime and currently active subscriber counts for the connected Webpushr site.
- Send Notification by Attributes
Create or schedule a push notification campaign for subscribers matching any supplied custom attribute key/value pair.
- Send Notification to All Subscribers
Create or schedule a push notification campaign for every subscriber of the connected Webpushr site. This can notify the entire audience and should only be called with explicit user intent.
- Send Notification to Segments
Create or schedule a push notification campaign for subscribers in one or more Webpushr segments. This sends to every subscriber in the selected segments and should only be called with explicit user intent.
- Send Notification to Subscriber
Send or schedule a push notification to one Webpushr subscriber ID. Use only when the intended recipient's subscriber ID is known.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Webpushr in the list and click Connect. 3. Log into your Webpushr dashboard, go to Settings > API Keys, and copy your Public Key and Auth Token. 4. Paste both values into the Switchy connection form and click Authorize. 5. Switchy confirms the connection by fetching your subscriber count — you'll see a success message if it works. 6. Inside any Project, type '@Webpushr get subscriber count' to verify the MCP responds. 7. To send a notification, use '@Webpushr send notification to segments' and specify the segment name and message content in your prompt. 8. Check the response for a campaign ID, then query delivery stats with '@Webpushr get notification status' and that ID.
What teammates see: by default, memories from Webpushr 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
Check Active Subscribers
@Webpushr get subscriber count for our site and show me both active and total numbers.
Launch Announcement to Beta
@Webpushr send notification to segments named 'Beta Testers' with the title 'New Feature Live' and message 'Try our redesigned dashboard now' linking to https://app.example.com/dashboard.
Re-Engage Inactive Users
@Webpushr send notification by attributes where 'last_active' is 'over_30_days' with title 'We Miss You' and message 'Come back for 20% off your next order'.
Urgent Outage Alert
@Webpushr send notification to all subscribers with title 'Service Interruption' and message 'We're investigating login issues and expect resolution within 30 minutes'.
Review Campaign Performance
@Webpushr get notification status for campaign ID 987654 and summarize how many people opened it versus dismissed it.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@webpushr what's the current subscriber count and how did our last campaign perform?
Your Webpushr site has 12,847 lifetime subscribers with 8,203 currently active. For your most recent campaign (ID: camp_xyz789), here's the breakdown: 7,891 notifications sent, 7,654 delivered (96.9%), 1,203 clicked (15.3% CTR), 89 closed. The campaign was sent 3 hours ago and delivery is complete.
This example combines two read operations—subscriber metrics and campaign analytics—to give a quick health check. Requires API key with read permissions. Campaign IDs must be known or retrieved separately; this MCP doesn't list all campaigns, so you'll need to track IDs from previous sends or check the Webpushr dashboard.
@webpushr send a push notification to all subscribers: 'Flash Sale: 30% off ends in 2 hours' with link to /sale
Push notification created and queued for immediate delivery to all 8,203 active subscribers. Campaign ID: camp_abc456. Title: 'Flash Sale: 30% off ends in 2 hours'. Target URL: https://yoursite.com/sale. Estimated delivery: 2-5 minutes depending on subscriber distribution. You can check delivery status by asking for camp_abc456 metrics in a few minutes.
This demonstrates the broadcast action—highest impact, highest risk. The MCP will send to your entire audience without confirmation prompts, so only use this when you explicitly intend a site-wide push. Rate limits apply (check your Webpushr plan tier). Consider testing with a segment first for time-sensitive campaigns to avoid costly mistakes.
@webpushr draft three notification variants for our premium_user segment announcing the new dashboard feature, then send the one with the strongest call-to-action
Here are three variants for your premium_user segment (1,204 subscribers): 1. 'Your new dashboard is live—see what's changed' → /dashboard/tour 2. 'Explore 5 new analytics views in your upgraded dashboard' → /dashboard/analytics 3. 'Try the new dashboard now and share feedback for early access perks' → /dashboard?survey=true Variant 3 has the strongest CTA with incentive. Sending now to segment 'premium_user'. Campaign ID: camp_def789. Delivery starts in ~90 seconds.
This showcases AI reasoning paired with segmented delivery. The MCP handles the send-to-segment action; the AI generates copy variations. Segment names must exist in your Webpushr account. This workflow is safer than all-subscriber blasts but still irreversible once sent—review AI-generated copy before confirming, especially for compliance-sensitive industries.
Use-case deep-dives
When Webpushr beats email for time-sensitive product drops
A 6-person DTC brand runs weekly flash sales and needs to notify 12,000 subscribers the instant inventory goes live. Webpushr's segment-based sending hits phones in under 30 seconds, while their email provider queues for 8-12 minutes. The team uses Send Notification to Segments during Thursday morning standups to schedule Friday's drop, then pulls Get Notification Status 10 minutes post-launch to confirm delivery before they tweet the sale link. This works because their subscriber base opted in and expects these alerts. If your audience didn't explicitly choose push or your cadence exceeds twice weekly, you'll see unsubscribe spikes that kill the channel. Webpushr wins here when speed matters more than message length and your list is genuinely engaged.
Attribute-based notifications for lifecycle marketing at scale
A 3-person growth team at a project management SaaS sends trial-ending reminders to 400 new signups weekly. They tag users with a custom attribute trial_ends_in_days and use Send Notification by Attributes to reach everyone at the 3-day and 1-day marks without manual list exports. Get Subscriber Count runs in their Monday sync to track opt-in health alongside email list size. This setup works because the team already maintains attribute hygiene in their product database and syncs it to Webpushr via webhook. If your user attributes live in five different tools or update inconsistently, you'll send mistimed notifications that feel spammy. Webpushr fits when your lifecycle stages are clean and you need a second channel that doesn't compete with transactional email for inbox space.
All-subscriber broadcasts for editorial teams under deadline pressure
A 9-person newsroom covers local government and breaking incidents in a mid-sized city. When a story hits that demands immediate reach—a school closure, a wildfire evacuation—the on-duty editor uses Send Notification to All Subscribers to push an alert to 18,000 readers in one action. Get Notification Status confirms delivery within 90 seconds so the team knows whether to follow up on social. This works because their audience subscribed specifically for breaking alerts and the team sends fewer than 5 all-subscriber pushes per month. If your content calendar is daily or your stories aren't genuinely urgent, subscribers will disable notifications and you lose the channel permanently. Webpushr is the right call when editorial judgment gates every send and speed to phones is non-negotiable.
Frequently asked
What does the Webpushr MCP let me do in Switchy?
It lets you send browser push notifications to your website subscribers directly from Switchy's AI workspace. You can target all subscribers, specific segments, individual subscriber IDs, or people matching custom attributes. You can also check campaign delivery stats and see how many active subscribers you have.
Do I need admin access to connect Webpushr?
You need a Webpushr API key, which typically requires account owner or admin permissions to generate. The key authenticates every notification send and data query, so whoever connects it in Switchy controls what the team can broadcast. Store the key securely — it grants full send access to your subscriber base.
Can the MCP schedule notifications for later or only send immediately?
Every send tool supports scheduling. You can create a campaign to go out immediately or set a future timestamp. This applies whether you're notifying all subscribers, a segment, a single ID, or an attribute match. Scheduled campaigns still count against your Webpushr plan limits the moment they're queued.
How is this different from using Webpushr's dashboard?
Switchy's MCP lets your team trigger notifications from AI prompts without logging into Webpushr. You lose the visual campaign builder and A/B testing UI, but gain the ability to send contextual pushes mid-conversation — useful when you're already discussing content or timing in Switchy and want to execute immediately.
Who on the team should connect this integration?
Whoever manages your push notification strategy and has the Webpushr API key. Once connected, any Switchy team member can send to all subscribers or large segments, so treat this like giving broadcast access. If you want tighter control, connect it under a dedicated service account and limit which Switchy channels can use it.