AgentPing

io.github.NorigetPublished by GitHub account Norigetv1.0.0Updated Oct 25, 2026

Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.

The publisher's own server: AgentPing

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

AgentPing is a hosted remote MCP server with one tool that lets an AI agent send you notifications by email, Slack, Discord, or a custom webhook.

What you can do
Send notifications: one tool, send_notification, takes a required title, an optional message, and an optional channel (all, email, slack, discord, or webhook), defaulting to every configured channel. Notify on completion, approval requests, results, or errors from long-running or autonomous agent runs. Deliver to whichever destinations you set up in your AgentPing account.
When to use it
Useful when an agent runs unattended and you want to be reached when a task finishes, needs approval, produces a result, or fails. Not needed for interactive sessions where you are already watching the output.
Requirements
A remote Streamable HTTP endpoint; no local runtime needed for the direct connection, though a stdio bridge via npx mcp-remote is documented for clients without header support. A free API key from the provider's signup page, sent as an Authorization bearer header. Destinations (email, Slack, Discord, webhook) must be configured in the account.
Before you install
The API key is a secret sent in the Authorization header; keep it private. Notifications leave your machine and go to the provider and to the channels you configure, so message content is shared with those third parties. The free tier is limited to 100 notifications per month; a paid Pro tier is offered. The README states it is read-only and can only send notifications, with no access to your inbox, files, or accounts.

Installation

In SourceWeft

  1. Open AgentPing in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Noriget%2Fagentping/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentping": {
      "type": "http",
      "url": "https://ping.mgm-llc.org/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[AgentPing logo]

AgentPing

Let your AI agent notify you — by email, Slack, Discord, or webhook.
A hosted, remote MCP server. One tool: send_notification.

Website · Docs · Get an API key (free)

▶ Get your free API key → ping.mgm-llc.org/signup


What it does

Long-running agents work while you're away. AgentPing gives them a send_notification tool so they can reach you the moment something matters:

  • ✅ Task done — "Migration finished, 3,412 rows updated."
  • 🙋 Approval needed — "Ready to deploy to prod. Confirm?"
  • 📊 Here's the result — daily summary, scrape output, build status.
  • 🚨 Something broke — error alerts from an autonomous run.

Notifications go to any channel you configure: email, Slack, Discord, or a custom webhook.

🔒 Read-only by design. AgentPing can only send the notifications your agent triggers. It has no access to your inbox, files, or accounts.

Connect it (MCP client config)

A. Remote URL — Cursor and any client that supports Streamable HTTP:

json
{  "mcpServers": {    "agentping": {      "url": "https://ping.mgm-llc.org/mcp",      "headers": { "Authorization": "Bearer YOUR_API_KEY" }    }  }}

B. Stdio bridge — works with every MCP client (incl. Claude Desktop):

json
{  "mcpServers": {    "agentping": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://ping.mgm-llc.org/mcp", "--header", "Authorization: Bearer YOUR_API_KEY"]    }  }}

Get your API key by signing up at ping.mgm-llc.org and setting your destinations. See the full docs for per-client steps and Slack/Discord webhook setup.

Tool

ToolArgumentsNotes
send_notificationtitle (string, required), message (string, optional), channel (optional)channel ∈ all | email | slack | discord | webhook. Default: all configured channels.

Pricing

  • Free — 100 notifications/month.
  • Pro — $9/mo or $90/yr — 10,000 notifications/month.

Protocol

Stateless Streamable HTTP (JSON-RPC 2.0): initialize, tools/list, tools/call, ping. Auth via Authorization: Bearer <api_key> (or ?key= for clients that can't set headers).

Self-hosting

Built on Cloudflare Workers + D1 + Hono. To run your own instance:

bash
npm installnpm run db:localnpm run dev            # http://localhost:8787

.dev.vars needs APP_SECRET (and RESEND_API_KEY to enable email).

bash
npx wrangler loginnpx wrangler d1 create agentping       # put database_id in wrangler.jsoncnpm run db:remotenpx wrangler secret put APP_SECRETnpx wrangler secret put RESEND_API_KEY# Stripe billing (optional):npx wrangler secret put STRIPE_SECRET_KEYnpx wrangler secret put STRIPE_WEBHOOK_SECRETnpx wrangler deploy

Set vars.APP_URL to the production URL and attach a custom domain.

License

MIT · Operated by MGM LLC.

Source: README.md at commit 61fbf3e

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Agentping integrations