Task Scheduler
by memoryapi.org · remote · no sign-in to list tools · v1.0.0 · published by org.memoryapi
Schedule and manage recurring or one-shot tasks
4 tools: 1 can delete or cancel things, 2 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http cron https://cron.memoryapi.org/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
4 tools
Deletes or cancels 1Claude Code: deny
cancel_scheduleCancel an active cron schedule to stop all future executions immediately.No findings
Why it is in this group
- The name "cancel_schedule" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel an active cron schedule to stop all future executions immediately.
Changes things 2Claude Code: ask
check_scheduleCheck the status of a cron schedule — is it active, when does it next run, how many times has it executed?No findings
Why it is in this group
- The name "check_schedule" says "schedule": a word for a change.
Description, as the server wrote it Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?
schedule_taskRegister a persistent cron schedule that runs even when your agent session ends.No findings
Why it is in this group
- The name "schedule_task" says "schedule": a word for a change.
Description, as the server wrote it Register a persistent cron schedule that runs even when your agent session ends. Specify a URL to call, how often, and for how long.
Only reads 1Claude Code: allow
get_execution_historyView recent execution history for a schedule — status codes, response previews, and timing.No findings
Why it is in this group
- The name "get_execution_history" says "get": a word for reading.
Description, as the server wrote it View recent execution history for a schedule — status codes, response previews, and timing.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cron https://cron.memoryapi.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cron__get_execution_history"
],
"ask": [
"mcp__cron__schedule_task",
"mcp__cron__check_schedule"
],
"deny": [
"mcp__cron__cancel_schedule"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as cron. Review it before you use it.