As of 2026-11-11, a native Claude cron job means a scheduled prompt: Claude Cowork scheduled tasks run hourly, daily, weekly, on weekdays or on demand on every paid plan, and cloud scheduled tasks (formerly routines) run Claude Code prompts in Anthropic's cloud. Neither gives your own endpoint a recurring HTTP request with retries, per-run history and failure alerts. Adding Crontap as a custom connector fills that gap: Claude calls Crontap's MCP tools to create and inspect the schedule, and Crontap sends each request on its own clock without opening a Claude conversation.
Suppose your team owns https://example.com/team/weekly-status and wants it called every Monday at 8:30 AM New York time. This guide has an organization owner add Crontap, lets a member connect it, creates the recurring HTTP job, and reads it back. Crontap calls the endpoint whether or not Claude is open.
Before you create a Claude cron job
- You need a Crontap account and a public HTTPS endpoint that is safe to retry.
- Anthropic documents custom remote MCP connectors for Free, Pro, Max, Ultra, Team, and Enterprise. Free accounts are limited to one custom connector.
- On Team, Owners and Primary Owners add custom connectors to the organization. Enterprise also allows a custom role with the "Manage access to Libraries" permission. Members then connect individually.
- Verified from Anthropic's custom connector guide, Cowork scheduled tasks article, and cloud scheduled tasks docs on 2026-11-11.
Connect Claude to Crontap MCP
Claude
1. Open Customize, then Connectors.
2. Choose "+", then Add custom connector.
3. Enter https://mcp.crontap.com/mcp as the remote MCP server URL.Connector availability can depend on your Claude plan and workspace policy.
For an individual account, the documented path is Customize > Connectors > + > Add custom connector. Enter https://mcp.crontap.com/mcp, add it, then authenticate. For Team and Enterprise, an owner first uses Organization settings > Connectors > Add > Custom > Web. A member then opens Customize > Connectors and selects Connect.
Step 1
Add the custom connector
Follow the path for your account type and enter the Crontap remote MCP URL. Crontap should appear in the connector list with a Custom label or its service name. In a managed workspace, the owner can now tell members it is ready.
Step 2
Complete OAuth and enable it
Select Connect, sign in to Crontap, and review the permissions. In a chat, use
the lower-left + menu, open Connectors, and enable Crontap for that
conversation. Claude can then see the Crontap tools in its Search and tools
menu under the member's own authorization.
- Crontap
- Connected
- Authentication
- OAuth 2.1
Step 3
Preview the team cadence
Ask Claude to preview “Mondays at 8:30am” in America/New_York, without
creating anything. preview_schedule should return the resolved cron
expression, timezone, and next run times. Check that every date lands on a
Monday for the team.
Step 4
Create the shared status request
Ask Claude to create a POST schedule named weekly team status for
https://example.com/team/weekly-status using the preview. Review the tool
input when Claude asks for approval. The write returns one schedule ID, active
status, and a next run.
Step 5
Hand the verified ID to the team
Ask Claude to list schedules, choose the new item, and retrieve it by ID. The stored URL, method, timezone, and cadence should match the preview. Share the non-secret schedule ID with teammates so later changes target the same resource. Pause it before correcting a mismatch.
Create the Claude cron job with copyable prompts
These prompts move from an owner-installed connector to a member-authorized schedule without sharing Crontap credentials.
Use the Crontap connector to preview "Mondays at 8:30am" in America/New_York. Make no changes. Show the resolved cron and three upcoming runs.Create a Crontap schedule named "weekly team status" that POSTs to https://example.com/team/weekly-status using the cadence we previewed. Summarize the exact tool input before asking me to approve it.List my schedules, find "weekly team status", retrieve it by ID, and report the URL, method, timezone, status, and next run. Keep the resource unchanged.Verify the Claude cron job worked
Verification has two halves. In Claude, inspect the returned ID and ask for the schedule again. This confirms that a saved Crontap resource exists, rather than Claude merely describing what it would create. In Crontap, open the same schedule and compare the endpoint, method, timezone, cadence, and status.
After its first fire, ask Claude to retrieve schedule history. A successful HTTP status means Crontap reached your route. Check your application's logs for the corresponding request and business action. If Crontap records a timeout or a 500 response, the schedule fired and the endpoint failed. If no history row exists after the expected time, investigate the cadence, timezone, and paused state first.
Keep API tokens out of the connector URL. Crontap authentication is handled through OAuth. Endpoint-specific secrets belong in request headers and should be handled with the smallest exposure your workflow allows.
Claude scheduled tasks or a Crontap schedule?
Claude now has two native ways to repeat work, and both run a Claude prompt. Last verified 2026-11-11 against Anthropic's Claude docs.
| Question | Claude scheduled tasks | Crontap schedule |
|---|---|---|
| What fires | A Claude prompt | An HTTP request to your URL |
| Plans | Pro, Max, Ultra, Team, Enterprise | Every Crontap plan |
| Shortest cadence | Hourly | 1 minute paid, hourly on Starter |
| Needs your computer awake | No, unless a task needs local files | No |
| Retries and failure alerts | Not documented for an HTTP call | Retries 5xx and timeouts, then alerts |
| Cadence options | Hourly, daily, weekly, weekdays | Any cron cadence, any IANA timezone |
Claude Cowork scheduled tasks are available on all paid plans. Anthropic says they run remotely, so they keep their cadence even when your computer is asleep. A task that needs local files or apps runs only on your computer. You pick hourly, daily, weekly, weekdays, or manual, and a task can use connectors, skills, and plugins.
A cloud scheduled task, formerly a routine, runs a Claude Code prompt in Anthropic's cloud. It is a research preview on Pro, Max, Ultra, Team, and Enterprise, created at claude.ai/code/routines, from the Desktop app, or with /schedule. Runs more often than once an hour are rejected, and on-the-hour runs can start several minutes late.
A Crontap schedule is the choice when the recurring unit of work is an HTTP request. It calls your endpoint independently of any Claude session, records status, status code, duration, and error for each run, and sends email failure alerts on every plan, with Slack, Discord, and Telegram on paid plans.
The two can be combined, but keep the roles plain: a Claude scheduled task runs Claude and may use the Crontap connector, for example to summarize last week's run history; Crontap owns HTTP schedules. If an existing agent process should prove it is alive, have it ping a Crontap heartbeat.
Troubleshoot the Claude connector
There is no Add custom connector button
Confirm your account and organization role. On Team and Enterprise, an owner must add the connector at organization level before members can connect it. Workspace policy can also disable connectors.
The connector is configured but Claude ignores it
Enable Crontap for the current conversation from the + menu under Connectors. You can also name the connector and tool directly in the prompt.
Authentication works locally but not in Claude
Claude connects to remote MCP servers from Anthropic's cloud, not from your device, including when you use Claude Desktop or Cowork. Private VPN-only endpoints need firewall allowlisting. Crontap's production URL is public, but a corporate network can still block the browser OAuth path.
A write tool is not offered
Open Search and tools and confirm the relevant Crontap tools are enabled. Start with list_schedules to prove the connector works, then ask explicitly for create_schedule.
The request returns 401 or 403
That response is usually from your scheduled endpoint, not the MCP connection. Check the endpoint header separately. Avoid reposting the secret into the conversation.
Next steps
- Return to the Crontap MCP hub for supported tools and connection security.
- Follow the CLI version in Claude Code or compare Cursor.
- Use Scheduled tasks for AI-built apps to make the endpoint idempotent and observable.
Once the owner has added the connector, any member can create the weekly status schedule from a chat, run a test against the endpoint, and share the returned ID with the team. Schedule your first job →
Verified against Claude custom connector and current Anthropic scheduling documentation on 2026-11-11. Sources: custom connectors, Claude Cowork scheduled tasks, and cloud scheduled tasks.
FAQ
Claude cron job questions
- Can Claude create cron jobs?
- Claude can call Crontap MCP tools to create recurring HTTP schedules. For recurring Claude prompts, Claude has its own scheduled tasks: Cowork scheduled tasks and cloud scheduled tasks (formerly routines) for Claude Code.
- Which Claude plans support custom connectors?
- Anthropic documents custom remote MCP connectors for Free, Pro, Max, Ultra, Team, and Enterprise. Free accounts are limited to one custom connector, and managed workspaces can impose additional policy.
- Can Claude schedule tasks without Crontap?
- Yes, for prompts. Claude Cowork scheduled tasks run hourly, daily, weekly, on weekdays or on demand on all paid plans, and run remotely while your computer sleeps. They run a Claude prompt, not a retried HTTP request to your endpoint.
- Can a Claude connector change a schedule?
- Yes. A connector can expose create, update, pause, resume, and delete tools. Review write approvals carefully and confirm the target schedule before changing it.
- Does Crontap schedule Claude prompts?
- No. Crontap schedules HTTP requests and manages monitors and heartbeats. When the recurring work is a Claude prompt, use a Claude Cowork scheduled task or a cloud scheduled task (formerly a routine).
