Reminder
MCP ServerFree** - MCP server for scheduling and triggering reminders via Slack or Telegram.
Capabilities7 decomposed
slack-based reminder scheduling and triggering
Medium confidenceImplements an MCP server that accepts reminder requests and schedules them for future execution, then delivers notifications via Slack webhooks or bot integrations. The system uses a scheduling backend (likely cron-based or interval-driven polling) to monitor registered reminders and trigger Slack message delivery at specified times, supporting both one-time and recurring reminder patterns through a standardized MCP protocol interface.
Exposes reminder scheduling as an MCP server primitive, allowing any MCP-compatible client (including Claude, LLM agents, or custom applications) to trigger reminders without implementing Slack API integration logic directly. This abstracts away webhook management and message formatting into a reusable service.
Simpler than building custom Slack bot logic for each agent; more flexible than hardcoded reminder systems because it's protocol-agnostic and composable with other MCP tools
telegram-based reminder scheduling and triggering
Medium confidenceProvides parallel reminder delivery capability via Telegram Bot API, allowing reminders to be sent to Telegram users or groups. The implementation integrates with Telegram's bot token authentication and message sending APIs, enabling the same scheduling backend to route notifications to Telegram instead of or in addition to Slack, with support for Telegram-specific message formatting and chat ID targeting.
Provides Telegram as a first-class notification channel alongside Slack within the same MCP server, allowing developers to abstract away platform-specific bot API differences and route reminders based on user preference or channel configuration without duplicating scheduling logic.
Offers platform parity with Slack integration in a single server; more maintainable than separate Slack and Telegram reminder services because scheduling logic is unified and only delivery mechanism differs
mcp protocol-based reminder request handling
Medium confidenceImplements the Model Context Protocol (MCP) server interface to accept reminder requests from MCP clients (such as Claude, custom LLM agents, or other MCP-compatible applications). The server exposes standardized MCP tools/resources for reminder creation, listing, and cancellation, translating MCP protocol messages into internal scheduling operations and returning structured responses that conform to MCP specification for tool results.
Exposes reminder functionality as a native MCP server rather than requiring custom tool wrappers or API clients, enabling seamless composition with other MCP tools in agent workflows and allowing Claude to schedule reminders with the same interface it uses for other MCP-based capabilities.
More composable than REST API wrappers because it integrates directly into MCP agent ecosystems; eliminates need for custom tool definitions or API client code in agent implementations
cron expression-based recurring reminder scheduling
Medium confidenceSupports scheduling reminders using cron expression syntax (e.g., '0 9 * * MON' for 9 AM every Monday), allowing users to define complex recurring patterns without custom logic. The implementation parses cron expressions and converts them into scheduled execution times, leveraging a cron scheduling library or custom parser to determine when reminders should trigger and managing the lifecycle of recurring reminder instances.
Integrates standard cron expression parsing into the MCP reminder server, allowing agents and developers to express recurring schedules using industry-standard syntax rather than custom scheduling DSLs or imperative scheduling code.
More expressive than simple 'repeat every N hours' patterns; more portable than custom scheduling logic because cron syntax is universally understood by operations teams
one-time reminder scheduling with absolute timestamps
Medium confidenceEnables scheduling reminders for a specific point in time (e.g., 'remind me at 2024-01-15 14:30 UTC'), storing the reminder with its target execution time and triggering delivery when the scheduled time arrives. The implementation compares current time against stored reminder timestamps and executes delivery when conditions are met, supporting both ISO 8601 timestamps and Unix epoch formats for maximum compatibility.
Provides simple absolute timestamp scheduling alongside cron-based recurring reminders, allowing the same server to handle both one-time and recurring use cases without requiring separate services or complex conditional logic.
Simpler than cron-based scheduling for one-time events; more flexible than hardcoded reminder times because timestamps can be dynamically generated by agents or users
reminder persistence and state management
Medium confidenceStores scheduled reminders in a persistent data store (implementation details unclear from available documentation, likely file-based JSON or database), maintaining reminder state across server restarts and allowing queries for active, completed, or cancelled reminders. The system tracks reminder metadata (ID, message, target channel, scheduled time, status) and provides mechanisms to list, update, or cancel reminders before execution.
unknown — insufficient data on whether persistence uses file-based JSON, embedded database, or external service; implementation details not documented in available sources
Provides durability guarantees that in-memory-only reminder systems lack; enables reminder management operations (list, cancel, modify) that stateless reminder services cannot support
multi-channel reminder routing with platform selection
Medium confidenceAllows reminders to be routed to Slack, Telegram, or both simultaneously based on configuration or per-reminder specification, with the server handling platform-specific formatting and delivery logic transparently. The implementation abstracts away platform differences through a unified reminder model and routes each reminder to one or more configured channels, handling failures in one channel without blocking others.
Unifies Slack and Telegram delivery within a single MCP server, allowing agents to specify 'send reminder to Slack and Telegram' without implementing separate integrations or managing platform-specific logic in agent code.
More maintainable than separate Slack and Telegram reminder services; more flexible than platform-specific solutions because routing can be configured per reminder or globally
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Reminder, ranked by overlap. Discovered automatically through the match graph.
@sigmacomputing/slack-mcp-server
MCP server for interacting with Slack
typescript-sdk
The official TypeScript SDK for Model Context Protocol servers and clients
@ampersend_ai/modelcontextprotocol-sdk
Model Context Protocol implementation for TypeScript
supergateway
Run MCP stdio servers over SSE, Streamable HTTP or visa versa
@sigmacomputing/slack-mcp-server
MCP server for interacting with Slack
slack-relay-mcp
Code-execution-based Slack MCP tool — CLI + TypeScript API + Claude Code skill
Best For
- ✓Teams using Slack as their primary communication platform
- ✓LLM agent builders needing asynchronous notification capabilities
- ✓Developers building MCP-compatible applications requiring reminder functionality
- ✓Teams or individuals using Telegram as primary communication tool
- ✓Global teams with Telegram preference in regions where Slack adoption is lower
- ✓Multi-channel notification strategies requiring platform diversity
- ✓LLM agent developers using Claude or other MCP-compatible models
- ✓Teams building multi-tool agent systems with standardized protocol requirements
Known Limitations
- ⚠Requires valid Slack webhook URL or bot token with message posting permissions
- ⚠No built-in persistence layer — reminders may be lost on server restart unless external state store is configured
- ⚠Scheduling precision depends on underlying polling interval; sub-second accuracy not guaranteed
- ⚠Single-server deployment has no distributed scheduling support for high-volume reminder scenarios
- ⚠Requires valid Telegram bot token with message sending permissions
- ⚠Telegram chat IDs must be pre-configured or discovered through separate mechanism
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - MCP server for scheduling and triggering reminders via Slack or Telegram.
Categories
Alternatives to Reminder
Are you the builder of Reminder?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →