Cronfree Time Scheduler for AI agents

Cronfree Time Scheduler creates and removes recurring webhook schedules, letting a workflow fire on a set cadence without running its own cron server. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Cronfree Time Scheduler See the 2 actions ↓

SchedulingAPI keyMCP + REST

AUDIT LOG · CRONFREE TIME SCHEDULERPOLICY: acme-support

09:41:09 · claude · u_8f2write

cronfree_time_scheduler.create_recurring_webhook_schedule

Create Recurring Webhook Schedule✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

cronfree_time_scheduler.remove_recurring_webhook_schedule

Remove Recurring Webhook Schedule✕ blocked · policy: deny

EVERY CRONFREE TIME SCHEDULER CALL, ON THE RECORD

01 · USE CASES

What agents do in Cronfree Time Scheduler.

Create a recurring schedule

Create a recurring webhook schedule that fires at a chosen day, hour, and timezone.

Remove a schedule no longer needed

Remove a recurring webhook schedule once the workflow it triggered is retired.

Set a schedule's timezone correctly

Create a schedule with the right timezone so it fires at the intended local time.

02 · ACTIONS

2 Cronfree Time Scheduler actions, graded by risk.

Every Cronfree Time Scheduler action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

No read actions.

write

Create and change things. Allow, or ask the user first.

cronfree_time_scheduler.create_recurring_webhook_schedule
Create Recurring Webhook Schedule

destructive

Delete, cancel or archive. Ask first, or deny outright.

cronfree_time_scheduler.remove_recurring_webhook_schedule
Remove Recurring Webhook Schedule

03 · HOW IT WORKS

Cronfree Time Scheduler in three steps.

01Your users connect Cronfree Time SchedulerThey add their Cronfree Time Scheduler api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, writes like “create Recurring Webhook Schedule” can wait for the user, and “remove Recurring Webhook Schedule” can be denied outright.
03Any agent can actYour agent calls Cronfree Time Scheduler through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('cronfree_time_scheduler', {
  read: 'allow',
  write: 'ask',        // create_recurring_webhook_schedule
  destructive: 'deny',  // remove_recurring_webhook_schedule
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How Cronfree Time Scheduler connects.

Users add their Cronfree Time Scheduler api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Cronfree Time Scheduler connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: API key
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use Cronfree Time Scheduler from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More scheduling apps.

Google Calendar50 actions

Calendly57 actions

Apaleo29 actions

Cal175 actions

Bookingmood142 actions

Eventbrite95 actions

Etermin78 actions

Ticket Tailor77 actions

ALL SCHEDULING APPS →

07 · FAQ

Cronfree Time Scheduler and Arc0, answered.

Q01

Can I use Cronfree Time Scheduler with Claude, ChatGPT or Cursor?

Yes. Connect Cronfree Time Scheduler to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Cronfree Time Scheduler actions you allow.

Q02

How do users connect Cronfree Time Scheduler?

Users add their Cronfree Time Scheduler api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Cronfree Time Scheduler actions can my agent take?

2 in total: 0 read, 1 write and 1 destructive, such as “create Recurring Webhook Schedule”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Cronfree Time Scheduler?

Yes. Actions like “remove Recurring Webhook Schedule” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Cronfree Time Scheduler too?

Yes. The same Cronfree Time Scheduler connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Cronfree Time Scheduler into your agent.

Your users connect Cronfree Time Scheduler once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.

Connect Cronfree Time Scheduler Browse all apps →

Free to build · MCP + REST · Audit log on every plan