AgentCron MCP Server

Schedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs. The agentcron mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

• ⏰ Remind later — "Notify me in 2 hours to review the PR."
• 🔁 Recurring — "Email me a summary every weekday at 9am."
• 🪝 Delayed webhook — "POST this URL in 30 minutes to resume the workflow."
• 🔍 Poll — "Every 10 minutes, hit the status webhook."

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• schedule_task — Schedule a notify or webhook task. Timing: in_seconds or run_at (ISO 8601 UTC); add repeat_every_seconds to recur
• list_tasks — List pending and recent tasks
• cancel_task — Cancel a pending task by id

Configuration

You will need 2 environment variables: YOUR_API_KEY, RESEND_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agentcron mcp server does with a few real requests.

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. AgentCron's toolset — schedule_task, list_tasks, cancel_task — is a fair guide to whether it matches your workflow. It is maintained by Noriget; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.