How to connect Pushbullet to Hermes Agent
Connect Pushbullet to Hermes with ClawLink: paste your Pushbullet key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
PushbulletAPI KEYMCPPush notifications, links, and files across devices. Once connected, Hermes Agent can read and act on Pushbullet from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Pushbullet access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Pushbullet setup: pair once in the browser and your always-on Hermes agent can act on Pushbullet for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Pushbullet.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Pushbullet
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Pushbullet?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Pushbullet in the ClawLink dashboard — paste your Pushbullet API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Pushbullet, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Pushbullet is connected in the dashboard, that agent calls the same 15 Pushbullet tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Pushbullet MCP for Hermes
Looking for a Pushbullet MCP server for Hermes Agent? ClawLink connects Pushbullet to Hermes Agent and exposes 15 Pushbullet tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Pushbullet integration works the same way.
What the Hermes Agent Pushbullet integration can do
15 Pushbullet tools are ready for Hermes Agent once the account is connected. The 11 below are the ones people reach for most; your agent can call all 15.
11 of 15 Pushbullet tools for Hermes
| Tool | What it does |
|---|---|
Get user pushbullet_get_user | Retrieve the currently authenticated user's profile |
List chats pushbullet_list_chats | List all chat objects for the current user |
List devices pushbullet_list_devices | List all registered devices for the current user |
List pushes pushbullet_list_pushes | List pushes with optional filtering and pagination |
Create chat pushbullet_create_chat | Create a new chat with the specified email address |
Create device pushbullet_create_device | Register a new device under the current user's account |
Create push pushbullet_create_push | Send a new push (note, link, or file) to a device, user, channel, or client |
Update chat pushbullet_update_chat | Mute or unmute an existing chat |
Update device pushbullet_update_device | Update metadata for a device by its identifier |
Update push pushbullet_update_push | Update a push (dismiss or modify list items) by its identifier |
Upload request pushbullet_upload_request | Obtain a signed upload URL for a file before pushing |
Try it: find the Pushbullet tool you need
Browse the 11 Pushbullet tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Pushbullet, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Pushbullet, group them by priority, and recommend what Hermes should do next.
List the relevant items in Pushbullet, group them by priority, and recommend what Hermes should do next.
List the relevant items in Pushbullet, group them by priority, and recommend what Hermes should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Pushbullet working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Pushbullet API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Pushbullet account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Pushbullet. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Pushbullet actions to the runtime in a format your agent can reliably use. | 15 tools for Pushbullet are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Pushbullet to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Pushbullet in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Pushbullet key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Pushbullet
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Pushbullet from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Pushbullet tools
Pushbullet tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Pushbullet call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Pushbullet returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Pushbullet has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Pushbullet integration?
Yes. ClawLink is the fastest way to connect Hermes to Pushbullet: link your Pushbullet account once in the browser and Hermes Agent can call the Pushbullet API through 15 ready-made tools — no custom code or token handling.
How do I connect Pushbullet to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Pushbullet in the dashboard and Hermes can use it from the next message — no config files, and the Pushbullet key you paste is stored server-side instead of in your environment.
How long does it take to connect Pushbullet to Hermes Agent?
About two minutes. Sign in, click Connect next to Pushbullet in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Pushbullet up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Pushbullet working from chat.
Hermes paired but still can't use Pushbullet
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
