How to integrate Pushover MCP with Hermes

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Pushover logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Pushover account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Pushover with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Pushover with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Pushover

Ask your agent to connect to Pushover, or simply request any Pushover-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Pushover connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Pushover or request any Pushover-related task. It will prompt you to authenticate and authorize access.

5. Done!

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.

Way Forward

With Pushover connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Pushover MCP Agent with another framework

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 Hermes?

Yes, you can. Hermes 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.