Integration

Pushbullet integration

Pushbullet API: send note, link and file pushes to your own devices, to another person by email or to a channel, list and dismiss or delete pushes, manage the devices registered on the account, manage chats and channel subscriptions, look up public channel information, read the account behind the token and reserve an upload slot for a file push. Authenticate with an access token from your account settings.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Pushbullet.Built from the 18 Pushbullet tools below, on the connection you add once.

Common Pushbullet use cases

  • validating a new Pushbullet credential
  • clearing the push history after a test run
  • polling for new pushes to drive a workflow
  • tidying up chats created by a test workflow
  • listing the recipients an account can push to
  • cleaning up pushes a workflow created for testing
  • removing the virtual device of a retired automation
  • subscribing an automation account to a status channel
  • unsubscribing from a channel that has become too noisy
  • preparing to push a generated report file to your devices

What you can do with Pushbullet

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Push, 5 operations

  • create_pushCreate pushPOSTSends a Pushbullet note, link or file push.
  • delete_all_pushesDelete all pushesDELETEDeletes every Pushbullet push on the account.
  • delete_pushDelete pushDELETEDeletes one Pushbullet push.
  • list_pushesList pushesGETLists Pushbullet pushes on the account, newest first.
  • update_pushUpdate pushPOSTMarks a Pushbullet push as dismissed on every device.

Device, 4 operations

  • create_deviceCreate devicePOSTRegisters a virtual Pushbullet device that pushes can be addressed to.
  • delete_deviceDelete deviceDELETERemoves a device from the Pushbullet account.
  • list_devicesList devicesGETLists the devices registered on the Pushbullet account.
  • update_deviceUpdate devicePOSTUpdates the nickname or metadata of a Pushbullet device.

Chat, 3 operations

  • create_chatCreate chatPOSTStarts a Pushbullet chat with a person identified by email.
  • delete_chatDelete chatDELETEDeletes a Pushbullet chat.
  • list_chatsList chatsGETLists the Pushbullet chats, meaning the people you push to.

Subscription, 3 operations

  • create_subscriptionCreate subscriptionPOSTSubscribes the Pushbullet account to a channel.
  • delete_subscriptionDelete subscriptionDELETEUnsubscribes the Pushbullet account from a channel.
  • list_subscriptionsList subscriptionsGETLists the Pushbullet channels the account is subscribed to.

Channel, 1 operation

  • get_channel_infoGet channel infoGETReturns public information about a Pushbullet channel from its tag.

Upload, 1 operation

  • request_file_uploadRequest file uploadPOSTReserves a Pushbullet upload slot and returns where to send the file bytes.

User, 1 operation

  • get_current_userGet current userGETReturns the Pushbullet account the access token belongs to.

Use Pushbullet from Claude Code, Cursor or Codex

Connect Pushbullet in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Pushbullet operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Pushbullet

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Pushbullet once

    Add your Pushbullet connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Pushbullet integration FAQ

What can you do with the Pushbullet integration?

LiveContext exposes 18 operations on Pushbullet, covering push, device, chat and subscription. Common uses include validating a new Pushbullet credential, clearing the push history after a test run and polling for new pushes to drive a workflow.

Popular integrations

Browse the whole catalog