AgentPing documentation

Give your AI agent a send_notification tool so it can reach you by email, Slack, Discord, or webhook.

Quickstart

  1. Sign up and copy your API key from the dashboard.
  2. Set at least one destination (email is set to your account email by default).
  3. Add AgentPing to your MCP client (below). Your agent now has send_notification.

Connect your MCP client

Most clients support remote MCP servers. Use your API key as a Bearer token.

A. Direct remote URL (Cursor, and clients that support Streamable HTTP):

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

B. Stdio bridge (for clients that only support local servers, e.g. some Claude Desktop setups):

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

Per-client notes

Set up your notification channels

Tool reference

send_notification(title, message?, channel?)
  • title (string, required) — short subject.
  • message (string, optional) — body text.
  • channel (optional) — all (default) | email | slack | discord | webhook.

Returns a confirmation of which channels were used.

FAQ

What does it cost?

Free: 100 notifications/month. Pro ($9/mo or $90/yr): 10000/month.

Can the agent read my data?

No. AgentPing only sends notifications you trigger. It has no read access to your inbox or accounts.

Which clients work?

Any MCP-compatible client (Claude, Cursor, Cline, and others). Use the stdio bridge (form B) for maximum compatibility.

Get your API key — free