How to integrate Pushbullet MCP with Codex

GET STARTED FOR FREE
Pushbullet logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Pushbullet MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Pushbullet with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Pushbullet MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Pushbullet MCP server, and what's possible with it?

The Pushbullet MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Pushbullet account. It provides structured and secure access to your Pushbullet devices, chats, and pushes, so your agent can perform actions like sending notifications, sharing files, managing chats, and organizing devices on your behalf.

  • Instant push notifications and file sharing: Instruct your agent to send notes, links, or files to any connected device, user, or channel for seamless cross-device updates.
  • Device management and registration: Let your agent list, register, or remove devices from your Pushbullet account to keep your ecosystem up to date.
  • Chat creation and management: Have your agent create new chat threads, list ongoing conversations, or delete chats as needed for streamlined communication.
  • Bulk push and chat cleanup: Direct your agent to delete individual pushes, clear all pushes at once, or remove old chats and devices to keep your space organized.
  • User profile access and verification: Enable your agent to retrieve your current Pushbullet user profile, ensuring secure and accurate operations every time.

Supported Tools & Triggers

Tools
Create ChatTool to create a new chat with the specified email address.
Register DeviceTool to register a new device under the current user's account.
Create PushTool to send a new push (note, link, or file) to a device, user, channel, or client.
Delete All PushesTool to delete all pushes for the current user asynchronously.
Delete ChatTool to delete a chat by its identifier.
Delete Pushbullet DeviceTool to remove a device by its identifier.
Delete PushTool to delete a specific push by its identifier.
Get current userTool to retrieve the currently authenticated user's profile.
List ChatsTool to list all chat objects for the current user.
List DevicesTool to list all registered devices for the current user.
List PushesTool to list pushes with optional filtering and pagination.
Register DeviceTool to register a new device under the current user’s account.
Delete All PushesTool to delete all pushes for the current user asynchronously.
Delete PushTool to delete a specific push by its identifier.
Mute or Unmute ChatTool to mute or unmute an existing chat.
Update DeviceTool to update metadata for a device by its identifier.
Update DeviceTool to update metadata for a device by its identifier.
Update PushTool to update a push (dismiss or modify list items) by its identifier.
Upload RequestTool to obtain a signed upload url for a file before pushing.

Conclusion

You've successfully integrated Pushbullet with Codex using Composio's MCP server. Now you can interact with Pushbullet directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Pushbullet operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Pushbullet operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Pushbullet MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Pushbullet MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Pushbullet MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Pushbullet MCP with Claude Code

OpenClaw logo

OpenClaw

Use Pushbullet MCP with OpenClaw

CLI logo

CLI

Use Pushbullet MCP with CLI

Google ADK logo

Google ADK

Use Pushbullet MCP with Google ADK

LangChain logo

LangChain

Use Pushbullet MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Pushbullet MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Pushbullet MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Pushbullet MCP with LlamaIndex

CrewAI logo

CrewAI

Use Pushbullet MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Pushbullet MCP?

With a standalone Pushbullet MCP server, the agents and LLMs can only access a fixed set of Pushbullet tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Pushbullet and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Pushbullet tools.

Can I manage the permissions and scopes for Pushbullet while using Tool Router?

Yes, absolutely. You can configure which Pushbullet scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Pushbullet data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free