Pingfyr MCP

What Pingfyr/mcp MCP server does

The Pingfyr/mcp MCP server gives an AI assistant access to Pingfyr’s reminder API. Agents can create scheduled deliveries, inspect existing reminders, change pending reminders, and cancel pending reminders. Delivery can target email, HTTP webhooks, Slack incoming webhooks, Discord webhooks, Telegram bots, OpenClaw endpoints, or a connected Google Calendar account.

A reminder requires a title, a future ISO 8601 fire time, a delivery channel, and one or more recipients. Optional fields include a message body, recurrence, timezone, custom metadata, and a cron expression for custom recurrence. Titles are limited to 200 characters and bodies to 2,000 characters.

How it works

The Pingfyr/mcp MCP server sends reminder operations to Pingfyr using the API key associated with the MCP connection. Once scheduled, reminders are handled by Pingfyr rather than requiring an external cron process or polling loop. Recurring reminders can use daily, weekly, monthly, or custom schedules. Timezones use IANA names and default to UTC when not specified.

The list_reminders tool supports status filtering for pending, processing, delivered, failed, and cancelled reminders. Results can be paginated with a limit and offset. Updates identify a reminder by UUID and apply to pending reminders; cancellation also applies to pending reminders.

Setup and configuration

Install the local package globally with npm or run it directly through npx. Local operation requires Node.js 18 or newer and uses stdio transport. Configure the MCP client to launch pingfyr-mcp and provide PINGFYR_API_KEY. The API key is obtained from Pingfyr after signing up.

Alternatively, use the hosted endpoint at https://mcp.pingfyr.com over HTTP. Set the same API key as a Bearer token in the request headers. Claude Code and Cursor support this HTTP configuration. Claude Desktop requires the local stdio configuration described in the README. PINGFYR_API_URL can override the default API base URL of https://pingfyr.com.

Tools and capabilities

The Pingfyr/mcp MCP server exposes four tools:

• create_reminder schedules a one-time or recurring delivery and accepts channel-specific recipients.
• list_reminders returns reminders with optional status filtering and pagination.
• update_reminder changes fields such as title, body, fire time, channel, recipients, recurrence, or timezone for a pending reminder.
• cancel_reminder cancels a pending reminder.

Webhook recipients are HTTP or HTTPS URLs, while Slack and Discord require their respective incoming webhook URLs. Telegram recipients use the bot:<bot_id>:<chat_id> format. OpenClaw uses an endpoint URL, and Google Calendar uses the literal recipient value google after the account is connected in Pingfyr.

Limitations and notes

Email and Google Calendar delivery require the Starter plan or higher. The Free plan includes webhook, Slack, Discord, Telegram, and OpenClaw channels. Account plans also impose monthly reminder and recipient limits: Free includes 50 reminders and 100 recipients per month, while higher plans provide larger or unlimited allowances.

The Google Calendar example requires a connected Google account, and Telegram requires a bot registered in Pingfyr settings. Custom recurrence requires a cron expression. API credentials must be supplied for either local or hosted use, and the README does not describe unauthenticated operation.