# How to integrate Pushover MCP with Pydantic AI ```json { "title": "How to integrate Pushover MCP with Pydantic AI", "toolkit": "Pushover", "toolkit_slug": "pushover", "framework": "Pydantic AI", "framework_slug": "pydantic-ai", "url": "https://composio.dev/toolkits/pushover/framework/pydantic-ai", "markdown_url": "https://composio.dev/toolkits/pushover/framework/pydantic-ai.md", "updated_at": "2026-05-12T10:23:05.620Z" } ``` ## Introduction This guide walks you through connecting Pushover to Pydantic AI 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 Pydantic AI 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/pushover/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/pushover/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/pushover/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/pushover/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/pushover/framework/codex) - [OpenClaw](https://composio.dev/toolkits/pushover/framework/openclaw) - [Hermes](https://composio.dev/toolkits/pushover/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/pushover/framework/cli) - [Google ADK](https://composio.dev/toolkits/pushover/framework/google-adk) - [LangChain](https://composio.dev/toolkits/pushover/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/pushover/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/pushover/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/pushover/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/pushover/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up your Composio API key and User ID - How to create a Composio Tool Router session for Pushover - How to attach an MCP Server to a Pydantic AI agent - How to stream responses and maintain chat history - How to build a simple REPL-style chat interface to test your Pushover workflows ## What is Pydantic AI? Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications. Key features include: - Type Safety: Built on Pydantic for automatic data validation - MCP Support: Native support for Model Context Protocol servers - Streaming: Built-in support for streaming responses - Async First: Designed for async/await patterns ## 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 | Tool slug | Name | Description | |---|---|---| | `PUSHOVER_CANCEL_RECEIPT_RETRIES` | Cancel Receipt Retries | Tool to cancel further retries for an emergency-priority message before its expiry. Use when you no longer want Pushover to keep attempting delivery of an urgent notification. | | `PUSHOVER_CANCEL_RETRIES_BY_TAG` | Cancel Retries by Tag | Tool to cancel retries for all active emergency-priority Pushover messages matching a specific tag. Use after sending emergency messages when you want to stop further retries for a given tag. | | `PUSHOVER_CLIENT_ACK_DELETE_UP_TO_ID` | Client Acknowledge Delete Up To ID | Tool to delete/acknowledge device messages up to a specific message ID. Use when you want to clear all messages up to a known ID; call after retrieving the latest message ID. | | `PUSHOVER_CLIENT_FETCH_MESSAGES` | Fetch Pending Messages | Tool to download pending messages for a registered device. Use after device registration to retrieve messages queued server-side. | | `PUSHOVER_CLIENT_LOGIN` | Pushover Client Login | Tool to authenticate a Pushover user by email and password. Use when you need to obtain a user key and session secret. Include twofa code if prompted by a prior HTTP 412 response. | | `PUSHOVER_CLIENT_REALTIME_WEBSOCKET` | Client Realtime WebSocket Connection | Tool to establish a secure WebSocket connection for real-time message notifications. Use after obtaining device ID and secret to receive instant push events. | | `PUSHOVER_CLIENT_REGISTER_DEVICE` | Register Open Client Device | Tool to register an Open Client desktop device. Use when you have a session secret from users/login to obtain a device ID. | | `PUSHOVER_GET_APP_ICON_IMAGE` | Get Application Icon Image | Tool to fetch an application icon PNG by icon identifier. Use when you need to retrieve and cache the Pushover app icon image. | | `PUSHOVER_GET_APP_LIMITS` | Get App Limits | Tool to retrieve the current monthly message limit, remaining messages, and reset time for a Pushover application. Use when monitoring your monthly quota before sending messages. | | `PUSHOVER_GET_APP_TOKEN` | Get Application Token | Tool to fetch stored Pushover application API token. Use when supplying credentials to other Pushover actions securely. | | `PUSHOVER_GET_RECEIPT_STATUS` | Get Receipt Status | Tool to poll the status of an emergency-priority notification receipt. Use after sending an emergency notification to check its delivery and acknowledgment. Use when you have the `receipt` from an emergency-priority message and need to track its retries and acknowledgment status. | | `PUSHOVER_GET_TEAM_API_TOKEN` | Get Team API Token | Tool to fetch stored Pushover for Teams API token. Use when supplying team credentials to other Pushover Teams actions securely. | | `PUSHOVER_GLANCES_UPDATE` | Glances Update | Tool to update a user's Glances widget data without sending a notification. Use after preparing glance data fields: title, text, subtext, count, or percent. | | `PUSHOVER_GROUP_ADD_USER` | Add User to Group | Tool to add an existing Pushover user to a delivery group. Use when you need to include a user in a group by their user key. | | `PUSHOVER_GROUP_CREATE` | Create Group | Tool to create a new Delivery Group. Use when you need to group multiple recipients under one group key before sending notifications. | | `PUSHOVER_GROUP_DISABLE_USER` | Disable Group User | Tool to temporarily disable deliveries to a user or specific device within a Pushover group. Use when suspending notifications for a user (or device) in an active group. | | `PUSHOVER_GROUP_ENABLE_USER` | Group Enable User | Tool to re-enable deliveries to a previously disabled user (or specific device) within a Pushover group. Use after disabling a user's or device's notifications to restore delivery. | | `PUSHOVER_GROUP_GET` | Get Group Details | Tool to retrieve details for a Delivery Group. Use when you need to fetch a group's name and member list. | | `PUSHOVER_GROUP_LIST` | List Delivery Groups | Tool to list all Delivery Groups. Use when you need to retrieve your account's delivery groups after obtaining a valid API token. | | `PUSHOVER_GROUP_REMOVE_USER` | Remove User from Group | Tool to remove a user (or optionally a specific device) from a Pushover delivery group. Use when you need to revoke a user's membership so they stop receiving group notifications. | | `PUSHOVER_GROUP_RENAME` | Rename Delivery Group | Tool to rename an existing Delivery Group. Use after confirming the group_key to update a group's name. | | `PUSHOVER_LICENSE_ASSIGN` | Assign License | Tool to assign a pre-paid license credit to a Pushover user by key or email. Use when you need to allocate a license and optionally restrict to a specific platform. | | `PUSHOVER_LICENSE_CHECK_CREDITS` | Check License Credits | Tool to retrieve remaining license credits for a Pushover application. Use when monitoring your licensing quota before assigning new licenses. | | `PUSHOVER_SEND_MESSAGE` | Send Message | Tool to send a push notification with optional title, URL, priority, sound, attachments, and filters. | | `PUSHOVER_STORE_TEAM_API_TOKEN` | Store Team API Token | Tool to securely store a Pushover for Teams API token. Use after obtaining a team API token to enable subsequent Teams actions. | | `PUSHOVER_SUBSCRIPTION_FLOW` | Subscription Flow | Tool to validate and return a Pushover subscription code. Use when Pushover does not support programmatic subscription creation and you need to confirm your code before redirecting users. | | `PUSHOVER_TEAMS_ADD_USER` | Add Team User | Tool to add a user to a Pushover for Teams organization. Use when inviting a user with optional admin rights, instant login link, or custom delivery group. | | `PUSHOVER_TEAMS_REMOVE_USER` | Remove User from Team | Tool to remove a user from a Pushover for Teams organization. Use when you need to revoke a user's access after confirming their email should be removed from the team. | | `PUSHOVER_VALIDATE_USER_OR_GROUP` | Validate User or Group | Tool to validate a Pushover user or group key for deliverability. Use before sending notifications to ensure the key (and optional device) is valid and has active devices. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Pushover MCP server is an implementation of the Model Context Protocol that connects your AI agent to Pushover. It provides structured and secure access so your agent can perform Pushover operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Python 3.9 or higher - A Composio account with an active API key - Basic familiarity with Python and async programming ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install the required libraries. What's happening: - composio connects your agent to external SaaS tools like Pushover - pydantic-ai lets you create structured AI agents with tool support - python-dotenv loads your environment variables securely from a .env file ```bash pip install composio pydantic-ai python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your agent to Composio's API - USER_ID associates your session with your account for secure tool access - OPENAI_API_KEY to access OpenAI LLMs ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key ``` ### 4. Import dependencies What's happening: - We load environment variables and import required modules - Composio manages connections to Pushover - MCPServerStreamableHTTP connects to the Pushover MCP server endpoint - Agent from Pydantic AI lets you define and run the AI assistant ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() ``` ### 5. Create a Tool Router Session What's happening: - We're creating a Tool Router session that gives your agent access to Pushover tools - The create method takes the user ID and specifies which toolkits should be available - The returned session.mcp.url is the MCP server URL that your agent will use ```python async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Pushover composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["pushover"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") ``` ### 6. Initialize the Pydantic AI Agent What's happening: - The MCP client connects to the Pushover endpoint - The agent uses GPT-5 to interpret user commands and perform Pushover operations - The instructions field defines the agent's role and behavior ```python # Attach the MCP server to a Pydantic AI Agent pushover_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[pushover_mcp], instructions=( "You are a Pushover assistant. Use Pushover tools to help users " "with their requests. Ask clarifying questions when needed." ), ) ``` ### 7. Build the chat interface What's happening: - The agent reads input from the terminal and streams its response - Pushover API calls happen automatically under the hood - The model keeps conversation history to maintain context across turns ```python # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Pushover.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() ``` ### 8. Run the application What's happening: - The asyncio loop launches the agent and keeps it running until you exit ```python if __name__ == "__main__": asyncio.run(main()) ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Pushover composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["pushover"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") # Attach the MCP server to a Pydantic AI Agent pushover_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[pushover_mcp], instructions=( "You are a Pushover assistant. Use Pushover tools to help users " "with their requests. Ask clarifying questions when needed." ), ) # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Pushover.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You've built a Pydantic AI agent that can interact with Pushover through Composio's Tool Router. With this setup, your agent can perform real Pushover actions through natural language. You can extend this further by: - Adding other toolkits like Gmail, HubSpot, or Salesforce - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Pushover for workflow automation) This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations. ## How to build Pushover MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/pushover/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/pushover/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/pushover/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/pushover/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/pushover/framework/codex) - [OpenClaw](https://composio.dev/toolkits/pushover/framework/openclaw) - [Hermes](https://composio.dev/toolkits/pushover/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/pushover/framework/cli) - [Google ADK](https://composio.dev/toolkits/pushover/framework/google-adk) - [LangChain](https://composio.dev/toolkits/pushover/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/pushover/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/pushover/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/pushover/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/pushover/framework/crew-ai) ## Related Toolkits - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place. - [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action. - [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication. - [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack. - [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers. - [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity. - [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease. - [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace. - [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms. - [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates. - [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices. - [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels. - [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks. - [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission. - [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security. - [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere. ## Frequently Asked Questions ### 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 Pydantic AI? Yes, you can. Pydantic AI 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)