Read the connected user and devices, list explicit push pages and send note or link notifications with a customer Pushbullet access token. Native cursors and destination fields are preserved. Choose a device, email or channel when sending; omitting all targets uses the provider account-wide behavior. This four-command subset excludes file uploads and event streams.
What you can do (4)
What you can do
Available commands: 4 (3 read, 1 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Read the connected Pushbullet user — pushbullet.users.me |
Read |
List available target devices — pushbullet.devices.list |
Read |
List one page of pushes — pushbullet.pushes.list |
Read |
Send one note or link to an explicit target — pushbullet.pushes.create |
Write |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Pushbullet, then enter the issued values in the connection form below.
- Open Pushbullet Settings → Account and create an Access Token. Treat it as access to the connected account and revoke it when no longer needed. Paste it into this connection’s Pushbullet API token field, then save selected commands. Use devices.list to obtain device_iden and pushes.list with an explicit limit and cursor. For pushes.create choose a target device, email or channel; omitting targets follows Pushbullet’s account-wide behavior. Note pushes require body; link pushes require url. Create a separate scoped Tooluse.net API key for your AI client and keep the Pushbullet token out of the MCP URL.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Pushbullet API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Read the connected Pushbullet user — pushbullet.users.me
Run Read the connected Pushbullet user with Pushbullet. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List available target devices — pushbullet.devices.list
Run List available target devices with Pushbullet. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List one page of pushes — pushbullet.pushes.list
Run List one page of pushes with Pushbullet. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Optional | additionalProperties: false |
|
query.limit |
integer | Optional | minimum: 1; maximum: 500 |
|
query.cursor |
string | Optional | ||
query.modified_after |
number | Optional | minimum: 0 |
|
query.active |
boolean | Optional |
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Send one note or link to an explicit target — pushbullet.pushes.create
Run Send one note or link to an explicit target with Pushbullet. This command can change provider data. Review the target and input before invoking it.
This operation can change provider data. Review the input before allowing an agent to call it.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
body |
object | Required | additionalProperties: false |
|
body.type |
string | Required | enum: ["note","link"] |
|
body.title |
string | Optional | ||
body.body |
string | Optional | ||
body.url |
string | Optional | format: "uri" |
|
body.device_iden |
string | Optional | ||
body.email |
string | Optional | format: "email" |
|
body.channel_tag |
string | Optional | ||
body |
object | Required | anyOf[1] |
|
body.type |
— | Required | anyOf[1]; const: "note" |
|
body |
object | Required | anyOf[2] |
|
body.type |
— | Required | anyOf[2]; const: "link" |
Full JSON Schema
Example input
{
"body": {
"type": "note",
"title": "Example",
"body": "Hello",
"device_iden": "device-id"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.