Server facts
reminder-mcp
Project
- Author
- arifszn
- Repository
- github.com/arifszn/reminder-mcp
- License
- Not specified
- Category
- Communication
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 15
- Last commit
- Data as of
Tags
- Slack
- Telegram
- alert
- productivity
Overview
Slack and Telegram are the delivery destinations for reminder-mcp, which connects natural-language reminder requests to scheduling and management tools. Users can ask an LLM to set a reminder for a relative delay or a specified time, then retrieve their reminders or remove them. The tools cover reminder creation, listing, local-time lookup, and deletion. Deletion supports selecting reminders by title, removing processed reminders, or clearing all reminders. Scheduled reminders must be at least 2 minutes in the future.
Scheduling and notification delivery are handled by cron-job.org rather than depending on the MCP server remaining active. This allows scheduled messages to reach the selected platform while the server is stopped. Configuration uses a cron-job.org API key and a choice of Slack or Telegram. Slack delivery uses a channel webhook, while Telegram delivery uses a bot token and a chat ID for a user or group. The MCP connection uses stdio.
reminder-mcp setup notes
- reminder-mcp records stdio only; confirm a network transport upstream before planning remote access.
- reminder-mcp has no recorded license; confirm reuse terms in its repository.