Pushbullet

@pushbullet send a link to our staging environment https://staging.acme.io to my phone so I can test the mobile flow

Push sent successfully to your device 'iPhone 14'. The link to https://staging.acme.io has been delivered with the title 'Staging Environment'. You should receive a notification on your phone momentarily. This example illustrates a typical link-sharing workflow — in practice, you'd see a push identifier and timestamp confirming delivery to the target device registered in your Pushbullet account.

This example showcases Pushbullet's core strength: instant cross-device content sharing. Requires OAuth2 authorization with push creation scope. The MCP needs at least one device registered to your account; if no devices exist, the push will queue until a device connects.

@pushbullet create a chat with sarah@acme.io so we can coordinate the demo prep without cluttering Slack

Chat created successfully with sarah@acme.io. A new conversation thread is now available in your Pushbullet account. Sarah will receive an invitation to join the chat if she has Pushbullet installed. This example demonstrates initiating a direct messaging channel — the actual response includes a chat identifier you can reference for follow-up messages.

Highlights Pushbullet's messaging capability for ad-hoc collaboration outside your primary chat tool. The recipient must have a Pushbullet account to participate. Be aware this creates a persistent chat thread that remains until explicitly deleted; consider privacy implications when sharing sensitive coordination details.

@pushbullet list all my recent pushes and summarize which ones are links versus notes, then delete any older than 7 days

Retrieved 23 pushes from your account. Breakdown: 14 links (mostly documentation and staging URLs), 7 text notes (meeting reminders and quick todos), 2 file attachments. Of these, 9 pushes are older than 7 days. Deleted 9 expired pushes to clean up your history. This example illustrates combining read operations (listing pushes) with AI reasoning (categorization) and bulk cleanup (delete by age criteria).

Demonstrates how the AI can chain Pushbullet's read and delete tools to perform maintenance tasks. The delete operation is irreversible — pushes are permanently removed, not archived. Rate limits apply to bulk operations; deleting hundreds of pushes may require multiple API calls and take several seconds to complete.

When Pushbullet beats Slack for build alerts

A 3-person dev team ships to staging twice a day and needs instant mobile alerts when builds fail. Pushbullet wins here because the Create Push tool can target specific devices (your phone, not your laptop) and doesn't require the recipient to have Slack open. The OAuth2 flow is straightforward for a small team where everyone already uses Pushbullet personally. The trade-off: if you need threaded discussion about the failure, you're back in Slack anyway. This works when the notification is the end goal—'build broke, check your terminal'—not the start of a conversation. If your team is larger than 5 people or you need audit logs, stick with a dedicated ops tool.

Pushbullet for after-hours escalation paths

A 2-person support team covering different time zones uses Pushbullet to hand off urgent tickets without waking the off-shift person. The Create Chat tool starts a direct thread by email, and Create Push sends a link to the ticket with a note about context. This beats email because the push arrives on the phone lock screen instantly, and it beats Slack because the recipient doesn't need to be logged in. The boundary: if you're escalating more than 3-4 tickets a week, you need a proper on-call rotation tool with scheduling. Pushbullet is the right call when escalations are rare enough that you don't want to pay for PagerDuty but frequent enough that email gets lost.

When file pushes replace a photo upload portal

A 6-person field sales team needs to send site photos back to the home office for proposal decks. The Create Push tool with file type lets them send images directly from their phones to a shared channel without logging into a web portal or dealing with Dropbox links. The Delete All Pushes tool cleans up the channel after each project closes. This works when the photos are ephemeral (used once, then archived) and the team is small enough that a shared channel doesn't turn into noise. If you're collecting more than 20 photos a week or need version control, you need a real DAM system. Pushbullet is the call when the overhead of a proper upload flow costs more time than the photos are worth.