Task Scheduler MCP Server
org.memoryapi/cron
answering
Task Scheduler is answering right now. Last checked 4 min ago. It exposes 4 tools.
Schedule and manage recurring or one-shot tasks
Uptime history
41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
420 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add cron --transport http https://cron.memoryapi.org/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"cron": {
"url": "https://cron.memoryapi.org/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.cron]
url = "https://cron.memoryapi.org/mcp".cursor/mcp.json
{
"mcpServers": {
"cron": {
"url": "https://cron.memoryapi.org/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"cron": {
"url": "https://cron.memoryapi.org/mcp"
}
}
}Available tools 4
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
schedule
check_schedule
Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?
schedule_task
Register a persistent cron schedule that runs even when your agent session ends. Specify a URL to call, how often, and for how long.
cancel
cancel_schedule
Cancel an active cron schedule to stop all future executions immediately.
execution
get_execution_history
View recent execution history for a schedule — status codes, response previews, and timing.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://cron.memoryapi.org/mcp | streamable-http | answering | 412 ms | 4 min ago |
Task Scheduler — questions
Answers built from our own checks of this server.
What can Task Scheduler do?
It exposes 4 tools, read directly from the server on our last check. Among them: cancel_schedule, check_schedule, get_execution_history, schedule_task. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Task Scheduler working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 420 ms. The bar chart above shows every period we have measured.
How do I connect Task Scheduler?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Task Scheduler need an API key?
No. Task Scheduler completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Task Scheduler?
It answers our handshake in 420 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.