Message Mcp

Created By
gimjina year ago
Real-time push notifications and alert sounds free you from staring at the screen. While the AI works, you can comfortably enjoy a cup of coffee.
Overview

What is Message MCP?

Message MCP is a tool that provides real-time push notifications and alert sounds, allowing users to stay updated on AI task completions without constantly monitoring their screens.

How to use Message MCP?

To use Message MCP, install it via the command line using npx message-mcp@latest, and configure it to send notifications through desktop alerts, sounds, or emails.

Key features of Message MCP?

  • 💬 Instant Notifications: Desktop notifications for task completions.
  • 🔔 Sound Alerts: Audio reminders for important updates.
  • 📧 Email Notifications: Option to receive notifications via email.
  • 🧩 Webhook Support: Ability to send notifications to custom URLs.

Use cases of Message MCP?

  1. Notifying users when AI-generated tasks are completed.
  2. Alerting developers about the status of long-running processes.
  3. Sending email updates for task completions.

FAQ from Message MCP?

  • Can Message MCP notify me for any task?

Yes! It can notify you for any task you configure it to monitor.

  • Is Message MCP free to use?

Yes! Message MCP is free to use for everyone.

  • What platforms does Message MCP support?

It supports macOS, Linux, and Windows.

Server Config

{
  "mcpServers": {
    "message-mcp": {
      "command": "npx",
      "args": [
        "message-mcp@latest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gimjin
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
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.

a day ago