Can I use Pushbullet as a CLI?

Yes. KosmoKrator exposes a Pushbullet CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pushbullet through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pushbullet tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pushbullet credentials stored?

Pushbullet credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pushbullet MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

notifications

Pushbullet MCP Integration for Codex

Connect Pushbullet to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

5 functions 3 read 2 write Bearer token auth

Submit Pushbullet feedback View package source

Connect Pushbullet to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Pushbullet MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-pushbullet": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=pushbullet",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=pushbullet --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Pushbullet instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Pushbullet Tools Visible to Codex

Codex sees stable MCP tool names generated from the Pushbullet integration catalog.

MCP tool	Source function	Type	Description
`integration__pushbullet__pushbullet_list_pushes`	`pushbullet.pushbullet_list_pushes`	Read	List recent pushes (notifications) from Pushbullet. Returns push items including notes, links, and files.
`integration__pushbullet__pushbullet_create_push`	`pushbullet.pushbullet_create_push`	Write	Send a push notification via Pushbullet. Supports "note" (title + body) and "link" (title + body + URL) types.
`integration__pushbullet__pushbullet_delete_push`	`pushbullet.pushbullet_delete_push`	Write	Delete a push notification from Pushbullet by its unique identifier (iden).
`integration__pushbullet__pushbullet_list_devices`	`pushbullet.pushbullet_list_devices`	Read	List all devices registered with the current user's Pushbullet account. Returns device names, types, and identifiers.
`integration__pushbullet__pushbullet_get_current_user`	`pushbullet.pushbullet_get_current_user`	Read	Get the authenticated Pushbullet user's profile information, including name, email, and account details.

Related Pushbullet Pages

Pushbullet CLIUse direct JSON commands instead of MCP discovery. Pushbullet MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.