How to integrate Pushover MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Pushover logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Pushover to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Pushover agent that can send device alert for server downtime, notify me of new support tickets, push daily summary to your phone through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Pushover account through Composio's Pushover MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Pushover with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Pushover
  • Configure an AI agent that can use Pushover as a tool
  • Run a live chat session where you can ask the agent to perform Pushover operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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

The Pushover MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Pushover account. It provides structured and secure access to your notification system, so your agent can send instant alerts, deliver custom messages, manage notification priorities, and automate device notifications on your behalf.

  • Instant push notifications: Have your agent send real-time alerts to your devices for important events, tasks, or reminders.
  • Custom message delivery: Allow your agent to craft and deliver personalized notifications with specific titles, messages, and sounds.
  • Priority and sound control: Let the agent set notification priority levels and choose custom sounds to ensure the right alerts stand out.
  • Device targeting: Direct your agent to send notifications to specific devices or user groups for tailored communication.
  • Automated workflow integration: Seamlessly trigger Pushover alerts from other automated tasks or events managed by your agent, keeping you informed in real-time.

Supported Tools & Triggers

Tools
Cancel Receipt RetriesTool to cancel further retries for an emergency-priority message before its expiry.
Cancel Retries by TagTool to cancel retries for all active emergency-priority Pushover messages matching a specific tag.
Client Acknowledge Delete Up To IDTool to delete/acknowledge device messages up to a specific message ID.
Fetch Pending MessagesTool to download pending messages for a registered device.
Pushover Client LoginTool to authenticate a Pushover user by email and password.
Client Realtime WebSocket ConnectionTool to establish a secure WebSocket connection for real-time message notifications.
Register Open Client DeviceTool to register an Open Client desktop device.
Get Application Icon ImageTool to fetch an application icon PNG by icon identifier.
Get App LimitsTool to retrieve the current monthly message limit, remaining messages, and reset time for a Pushover application.
Get Application TokenTool to fetch stored Pushover application API token.
Get Receipt StatusTool to poll the status of an emergency-priority notification receipt.
Get Team API TokenTool to fetch stored Pushover for Teams API token.
Glances UpdateTool to update a user's Glances widget data without sending a notification.
Add User to GroupTool to add an existing Pushover user to a delivery group.
Create GroupTool to create a new Delivery Group.
Disable Group UserTool to temporarily disable deliveries to a user or specific device within a Pushover group.
Group Enable UserTool to re-enable deliveries to a previously disabled user (or specific device) within a Pushover group.
Get Group DetailsTool to retrieve details for a Delivery Group.
List Delivery GroupsTool to list all Delivery Groups.
Remove User from GroupTool to remove a user (or optionally a specific device) from a Pushover delivery group.
Rename Delivery GroupTool to rename an existing Delivery Group.
Assign LicenseTool to assign a pre-paid license credit to a Pushover user by key or email.
Check License CreditsTool to retrieve remaining license credits for a Pushover application.
Send MessageTool to send a push notification with optional title, URL, priority, sound, attachments, and filters.
Store Team API TokenTool to securely store a Pushover for Teams API token.
Subscription FlowTool to validate and return a Pushover subscription code.
Add Team UserTool to add a user to a Pushover for Teams organization.
Remove User from TeamTool to remove a user from a Pushover for Teams organization.
Validate User or GroupTool to validate a Pushover user or group key for deliverability.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Pushover account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Pushover functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Pushover
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["pushover"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Pushover
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Pushover tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Pushover
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Pushover and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Pushover
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["pushover"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Pushover tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Pushover through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Pushover MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Pushover MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Pushover MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Pushover MCP with Claude Cowork

Codex logo

Codex

Use Pushover MCP with Codex

OpenClaw logo

OpenClaw

Use Pushover MCP with OpenClaw

Hermes logo

Hermes

Use Pushover MCP with Hermes

CLI logo

CLI

Use Pushover MCP with CLI

Google ADK logo

Google ADK

Use Pushover MCP with Google ADK

LangChain logo

LangChain

Use Pushover MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Pushover MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Pushover MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Pushover MCP with LlamaIndex

CrewAI logo

CrewAI

Use Pushover MCP with CrewAI

FAQ

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

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

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK 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 Pushover tools.

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

Yes, absolutely. You can configure which Pushover 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 Pushover 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.

Get started for freeGet a demo↗