Cronty MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JWT_SECRET | No | JWT secret for bearer token authentication. Required if AUTH_DISABLED is not set. | |
| QSTASH_TOKEN | Yes | Your Upstash QStash token. | |
| AUTH_DISABLED | No | Set to 'true' to disable authentication for local development. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delete_scheduleA | Delete a scheduled notification by its ID. Permanently removes a cron schedule. The schedule will stop firing and cannot be recovered. Use the schedule_id returned from schedule_cron_notification. |
| get_current_timeA | Get the current date and time in UTC. Returns the current UTC timestamp in ISO 8601 format, useful for scheduling notifications or including timestamps in messages. |
| list_scheduled_notificationsA | List scheduled recurring notifications. Returns all recurring cron notification schedules. Optionally filter by a specific notification topic. Note: One-off scheduled notifications (created with schedule_notification) are not included as they are pending messages, not recurring schedules. |
| pause_scheduleA | Pause a scheduled notification. Temporarily stops a cron schedule from firing. The schedule configuration is preserved and can be resumed later. Use the schedule_id returned from schedule_cron_notification. |
| resume_scheduleA | Resume a paused scheduled notification. Reactivates a paused cron schedule. The schedule will resume firing at its next scheduled time. Use the schedule_id returned from schedule_cron_notification. |
| schedule_cron_notificationA | Schedule a recurring notification using cron syntax. Creates a persistent schedule that fires according to the cron pattern. The schedule continues indefinitely until deleted via the Upstash panel. The agent should determine the user's timezone by:
|
| schedule_notificationA | Schedule a one-off notification for a future time. Supports three input modes (use only one):
|
| send_push_notificationC | Send an immediate push notification. Sends a push notification for instant delivery. Only a message is required; all other parameters are optional. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_cron_examples | Common cron expression examples with descriptions. |
| get_valid_timezones | Common IANA timezones grouped by region. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cronty-com/cronty-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server