Skip to main content
Glama
cronty-com

Cronty MCP

Official
by cronty-com
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JWT_SECRETNoJWT secret for bearer token authentication. Required if AUTH_DISABLED is not set.
QSTASH_TOKENYesYour Upstash QStash token.
AUTH_DISABLEDNoSet to 'true' to disable authentication for local development.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
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

NameDescription
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:

  1. Checking system/environment timezone information

  2. If unavailable, asking the user explicitly

schedule_notificationA

Schedule a one-off notification for a future time.

Supports three input modes (use only one):

  1. datetime: ISO 8601 format (e.g., 2025-01-15T09:00:00+01:00)

  2. date + time + timezone: Separate parameters

  3. delay: QStash delay format (e.g., 1d, 2h30m, 1d10h30m50s)

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_cron_examplesCommon cron expression examples with descriptions.
get_valid_timezonesCommon IANA timezones grouped by region.

Latest Blog Posts

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