Pushover MCP

Created By
AshikNesina year ago
A MCP implementation for sending notifications via Pushover
Overview

what is Pushover MCP?

Pushover MCP is a Model Context Protocol implementation that allows AI agents to send notifications via Pushover.net.

how to use Pushover MCP?

To use Pushover MCP, you need to configure it with your Pushover application token and user key, then run the MCP server using npx or configure it in your project settings.

key features of Pushover MCP?

  • Seamless integration with MCP-compatible AI systems.
  • Ability to send customizable notifications through Pushover.
  • Supports various notification parameters like title, priority, and sound.

use cases of Pushover MCP?

  1. Sending alerts from AI systems to users.
  2. Notifying users about important events or updates.
  3. Integrating with other applications to provide real-time notifications.

FAQ from Pushover MCP?

  • What do I need to get started with Pushover MCP?

You need an application token and user key from Pushover.net.

  • Can I customize the notifications?

Yes! You can customize the message, title, priority, and sound of the notifications.

  • Is there a specific way to run the MCP server?

Yes, you can run it globally using npx or configure it in your project settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AshikNesin
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago