convez.ai
MCP ServerIntegração & APIsIntermediário
Noriget

AgentPing

Noriget/agentping

Notificações para agentes IA: email, Slack, Discord e webhooks

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que permite agentes de IA enviar notificações por email, Slack, Discord ou webhook. Ideal para alertas de conclusão de tarefas, aprovações pendentes e comunicados de erros em execuções autônomas.

Instalação

$npx convez-ai Noriget/agentping

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Alertar quando tarefas de longa duração terminam
  • Solicitar aprovação antes de ações críticas (deploy em prod)
  • Enviar resumos diários e resultados de scraping
  • Notificar falhas em execuções autônomas

Veredito

Solução robusta e bem integrada para conectar agentes IA a canais de notificação reais. Simples de usar (uma ferramenta: send_notification), com plano gratuito generoso (100 notificações/mês) e self-hosting possível.

README

A tradução para o português deste README ainda está na fila.


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:

{
  "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):

{
  "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:

npm install
npm run db:local
npm run dev            # http://localhost:8787

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

npx wrangler login
npx wrangler d1 create agentping       # put database_id in wrangler.jsonc
npm run db:remote
npx wrangler secret put APP_SECRET
npx wrangler secret put RESEND_API_KEY
# Stripe billing (optional):
npx wrangler secret put STRIPE_SECRET_KEY
npx wrangler secret put STRIPE_WEBHOOK_SECRET
npx wrangler deploy

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

License

MIT · Operated by MGM LLC.

Ver o original no GitHub

Bom para

Relacionados