MCP MeasureMCP Measure

index observed

Task Scheduler

Schedule and manage recurring or one-shot tasks

Should I use this

Quality & Safety

A
Description quality
95%
Schema completeness
98%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~409Tokens (tool definitions)
~928 BTypical response size
Minimal attention impact (0.32% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "cron": {
      "url": "https://cron.memoryapi.org/mcp"
    }
  }
}

Remote endpoints

https://cron.memoryapi.org/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪schedule_task(agent_id, url, method, body, interval_minutes, ...)

Register a persistent cron schedule that runs even when your agent session ends. Specify a URL to call, how often, and for how long.

Input Schema

{
  "type": "object",
  "properties": {
    "agent_id": {
      "type": "string",
      "description": "Your agent identifier"
    },
    "url": {
      "type": "string",
      "description": "HTTPS URL to call on each execution"
    },
    "method": {
      "type": "string",
      "description": "HTTP method: GET or POST (default: GET)",
      "default": "GET"
    },
    "body": {
      "type": "string",
      "description": "Optional JSON body for POST requests"
    },
    "interval_minutes": {
      "type": "number",
      "description": "How often to run (minimum 15 minutes)"
    },
    "duration_days": {
      "type": "number",
      "description": "How many days to keep running (max 30, default 7)",
      "default": 7
    }
  },
  "required": [
    "agent_id",
    "url",
    "interval_minutes"
  ]
}
🟢check_schedule(schedule_id, agent_id)

Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?

Input Schema

{
  "type": "object",
  "properties": {
    "schedule_id": {
      "type": "string",
      "description": "Schedule UUID from registration"
    },
    "agent_id": {
      "type": "string",
      "description": "Alternatively list all schedules for this agent"
    }
  }
}
🔴cancel_schedule(schedule_id, agent_id)

Cancel an active cron schedule to stop all future executions immediately.

Input Schema

{
  "type": "object",
  "properties": {
    "schedule_id": {
      "type": "string",
      "description": "Schedule UUID to cancel"
    },
    "agent_id": {
      "type": "string",
      "description": "Agent ID for ownership verification"
    }
  },
  "required": [
    "schedule_id"
  ]
}
🟢get_execution_history(schedule_id, limit)

View recent execution history for a schedule — status codes, response previews, and timing.

Input Schema

{
  "type": "object",
  "properties": {
    "schedule_id": {
      "type": "string",
      "description": "Schedule UUID"
    },
    "limit": {
      "type": "number",
      "description": "Number of executions to return (max 50)",
      "default": 10
    }
  },
  "required": [
    "schedule_id"
  ]
}

Recommended Prompts

retrieve_data
Get details about [item] from Task Scheduler
Expected tools: get_execution_history
fetch_info
Fetch [information type] using Task Scheduler
Expected tools: get_execution_history

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools