Pingfyr
Schedule future pings so long-running agent work gets nudged via email, webhook, Slack, Discord, Telegram, or Google Calendar instead of hoping you remember to check back.
Overview
Pingfyr MCP is a MCP server for the Operate phase that schedules agent-oriented reminders across email, webhooks, Slack, Discord, Telegram, and Google Calendar.
What is this MCP server?
- Hosted MCP at mcp.pingfyr.com with streamable-http and rm_ API key query param
- Delivery channels: email, webhook, Slack, Discord, Telegram, Google Calendar
- Purpose-built for scheduling reminders aimed at AI agents and their operators
- Open-source client reference at github.com/Pingfyr/mcp (v0.3.3)
- Server version 0.3.3
- 6 delivery channels listed: email, webhook, Slack, Discord, Telegram, Google Calendar
- Remote URL pattern: https://mcp.pingfyr.com/mcp?apiKey={apiKey}
What problem does it solve?
Async agent runs finish or stall without you noticing because nothing pings you at the right time across the channels you actually monitor.
Who is it for?
Solo builders orchestrating long MCP or agent sessions who want calendar-grade follow-ups without building custom cron + notifier code.
Skip if: Teams needing full incident paging, metrics dashboards, or deep workflow orchestration inside the repo.
What do I get? / Deliverables
Once Pingfyr is registered with your rm_ API key, your agent can set timed reminders that land on your chosen channel so you can iterate on outcomes reliably.
- Agent-scheduled reminders via up to six channel types
- Time-based follow-ups for long-running agent tasks without custom cron infrastructure
Recommended MCP Servers
Journey fit
Operate covers how you keep autonomous and semi-autonomous agents reliable in production; scheduled reminders are iteration hygiene for async workflows. Iterate fits timed follow-ups and human-or-agent checkpoints after ship, distinct from Build-time code integration or Launch distribution.
How it compares
Reminder and notification MCP, not desktop control or revenue analytics.
Common Questions / FAQ
Who is com.pingfyr/pingfyr for?
Developers using Claude Code, Cursor, or other MCP clients who run agent workflows and need scheduled reminders through common chat and calendar channels.
When should I use com.pingfyr/pingfyr?
In Operate when you want the agent to book a future check-in—for example after a deploy, data job, or human approval step—without writing your own scheduler.
How do I add com.pingfyr/pingfyr to my agent?
Create an rm_ API key at pingfyr.com dashboard settings, add the remote MCP URL https://mcp.pingfyr.com/mcp with apiKey, and register server id com.pingfyr/pingfyr in your client.