# How to integrate Pushover MCP with Google ADK ```json { "title": "How to integrate Pushover MCP with Google ADK", "toolkit": "Pushover", "toolkit_slug": "pushover", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/pushover/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/pushover/framework/google-adk.md", "updated_at": "2026-05-12T10:23:05.620Z" } ``` ## Introduction This guide walks you through connecting Pushover to Google ADK 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 Google ADK 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) - [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: - Get a Pushover account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Pushover - Build an agent that connects to Pushover through MCP - Interact with Pushover using natural language ## What is Google ADK? Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol. Key features include: - Gemini Integration: Native support for Google's Gemini models - MCP Toolset: Built-in support for Model Context Protocol tools - Streamable HTTP: Connect to external services through streamable HTTP - CLI and Web UI: Run agents via command line or web interface ## 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: - A Google API key for Gemini models - A Composio account and API key - Python 3.9 or later installed - Basic familiarity with Python ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key. - Copy the key and keep it safe. You will put this in GOOGLE_API_KEY. Composio API Key and User ID - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY. - Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Pushover via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables Save all your credentials in the .env file. What's happening: - GOOGLE_API_KEY authenticates with Google's Gemini models - COMPOSIO_API_KEY authenticates with Composio - COMPOSIO_USER_ID identifies the user for session management ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate environment What's happening: - os reads environment variables - Composio is the main Composio SDK client - GoogleProvider declares that you are using Google ADK as the agent runtime - Agent is the Google ADK LLM agent class - McpToolset lets the ADK agent call MCP tools over HTTP ```python import os import warnings from composio import Composio from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") ``` ### 6. Create Composio client and Tool Router session What's happening: - Authenticates to Composio with your API key - Declares Google ADK as the provider - Spins up a short-lived MCP endpoint for your user and selected toolkit - Stores the MCP HTTP URL for the ADK MCP integration ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["pushover"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent What's happening: - Connects the ADK agent to the Composio MCP endpoint through McpToolset - Uses Gemini as the model powering the agent - Lists exact tool names in instruction to reduce misnamed tool calls ```python composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Pushover operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening: - adk run runs the agent in CLI mode - adk web . opens a web UI for interactive testing ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```python import os import warnings from composio import Composio from composio_google import GoogleProvider from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider()) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["pushover"], ) COMPOSIO_MCP_URL = composio_session.mcp.url composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Pushover operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Pushover with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Pushover using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Pushover tools - Environment variables keep your credentials secure and separate from code - Clear agent instructions reduce tool calling errors - The ADK web UI provides an interactive interface for testing and development You can extend this setup by adding more toolkits to the toolkits array in your session configuration. ## 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) - [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 Google ADK? Yes, you can. Google ADK 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)