Back to MCP

MCP guides · Sep 15, 2026

Create an HTTP cron job with ChatGPT and Crontap

Test a harmless write in your real ChatGPT account, then use Crontap to create and verify a recurring HTTP request.
crontap.com / mcp guides
ChatGPT scheduled tasks run prompts daily, hourly on paid plans, or on Gmail, Slack and GitHub events. For a ChatGPT cron job that calls your HTTP endpoint with retries, history and alerts, add Crontap as a custom MCP server in Plugins, test a write, and create the schedule.

As of 2026-11-11, the closest thing to a ChatGPT cron job is a scheduled task: a prompt that runs daily or weekly (hourly or at exact times on eligible paid plans), or one that fires on a Gmail, Slack or GitHub event (not on Free or Go). What it cannot do is send a recurring HTTP request to your own endpoint, retry the call when it fails, keep a run history of status codes, and alert you when it breaks. Crontap's MCP server fills that gap: you add it to ChatGPT as a custom MCP server, ChatGPT calls its tools to create and check a hosted HTTP schedule, and Crontap then calls your endpoint on time without ChatGPT.

This guide connects ChatGPT to Crontap, proves that a harmless write works in your account, then creates a weekday HTTP schedule for https://example.com/daily-digest. The write test matters because full MCP access depends on your plan. Once created, Crontap calls the endpoint independently. It does not wake ChatGPT or turn this conversation into a recurring task.

Before you start

Which ChatGPT plans can create Crontap schedules

OpenAI's help article says custom MCP server connections and full MCP support are available for ChatGPT Business and Enterprise/Edu on ChatGPT web. Its FAQ adds that Pro users can connect custom MCP servers with read/fetch permissions only. Creating a Crontap schedule is a write, so on Pro you can list and read schedules but should expect writes to be unavailable.

On Business, only admins and owners can create a custom MCP plugin. Enterprise and Edu admins can grant that to other members through role-based access control.

One real ChatGPT account connected the production Crontap MCP server and completed a write tool on 2026-09-15. That confirms the tested account and flow, not every plan or workspace policy. Step 3 below tests your own account before the real schedule is created.

Connect ChatGPT to Crontap MCP

ChatGPT

1. Open Plugins, choose the plus button, then Add custom MCP server.
2. Enter https://mcp.crontap.com/mcp under Connection and choose OAuth.
3. Confirm the warning, then select Create as a plugin.

Custom MCP availability and write tools vary by plan, workspace policy, interface, and model. Test a write tool in the target account.

In the current Plugins experience, you add a custom MCP server directly from Plugins. You no longer need to turn on Developer mode first.

Step 1

Add a custom MCP server in Plugins

Open Plugins, select the plus button, and choose Add custom MCP server. Name it Crontap and enter https://mcp.crontap.com/mcp under Connection. If the option is missing, check your plan and ask a workspace admin about plugin permissions.

Step 2

Connect with OAuth

Choose OAuth as the authentication method, tick I understand and want to continue, and create it as a plugin. Complete Crontap sign-in when prompted. The plugin should list the Crontap tools your account can use.

Some workspaces still show the legacy path: Workspace settings > Apps > Create, then Scan Tools. The admin permission behind it is now called Create plugins with MCPs.

ChatGPT plugins
Crontap
Connected
Authentication
OAuth 2.1

Step 3

Run a harmless write test

Before creating the real schedule, ask ChatGPT to create a clearly named test schedule against a harmless endpoint you control, at a cadence you can inspect. Review and confirm the write tool. Then retrieve it and delete the test schedule with a second explicit confirmation. Both the test create and cleanup should succeed in this account.

Step 4

Preview the production cadence

Ask ChatGPT to preview “weekdays at 9am” in America/Los_Angeles without saving. preview_schedule should return the resolved cron, timezone, and upcoming dates. This read also confirms the plugin is selected for the message.

Step 5

Create and verify the HTTP job

Ask for a POST schedule named weekday daily digest targeting https://example.com/daily-digest. Confirm the tool after reviewing the payload, then retrieve the returned ID. You should see one active schedule with the previewed cadence and correct next run.

Ask ChatGPT with copyable prompts

Type @ and pick the Crontap plugin in each message that needs fresh tool data. Mention it again in follow-ups that need new data.

Use only the Crontap plugin. First list my schedules. Then create a temporary schedule named "mcp write test 2026-09-15" against my harmless test endpoint. Show the full non-secret input and ask for confirmation before the write. Retrieve the created schedule by ID. Do not create the real daily-digest schedule yet.
Use Crontap to preview "weekdays at 9am" in America/Los_Angeles. Do not write anything. Show the resolved cron and three upcoming runs.
Create a POST schedule named "weekday daily digest" for https://example.com/daily-digest using the cadence we previewed. Ask for confirmation, then retrieve the created schedule and report its ID, status, timezone, and next run.

Verify the ChatGPT cron job worked

Expand the tool call and inspect its input and output. The result should contain a schedule ID. Ask ChatGPT to list schedules and retrieve that ID without changing it.

Open Crontap separately and compare the endpoint, method, timezone, cadence, and active state. After the first run, read schedule history. A recorded 2xx confirms that Crontap got an HTTP success response. Check application logs to confirm the route performed the intended work.

If your write test fails but reads succeed, you are probably on Pro's read/fetch access, or workspace action controls disable the write. Check the plugin's enabled actions and ask an admin to confirm policy. Rewording cannot unlock a write the plan or policy disallows.

ChatGPT Scheduled Tasks or Crontap?

QuestionChatGPT scheduled tasksCrontap schedule
What repeatsA ChatGPT promptAn HTTP request to your URL
CadenceDaily on Free, hourly when paidCron expression, IANA timezone
Event triggersGmail, Slack, GitHub (not Free or Go)None, time only
Active task cap3 to 15, by planSet by your Crontap plan
When a run failsYou check the task outputRetries, run history, alerts

Last verified 2026-11-11 against OpenAI's ChatGPT help docs.

Use ChatGPT Scheduled Tasks when you want ChatGPT itself to do recurring work and notify you. Free tasks run no more than once a day, and hourly schedules and exact times need an eligible paid plan. Active tasks are capped at 3 on Free and Go, 5 on Plus, 10 on Business and Edu, and 15 on Pro and Enterprise.

Use Crontap when you want a recurring HTTP request to your API, webhook, or cloud function. New schedules retry 5xx responses, timeouts and network failures by default, history records each run's status, duration and error, and failures reach you by email. The same MCP connection also manages uptime monitors and heartbeats. Creating a Crontap schedule does not cause ChatGPT to return to this chat later.

Troubleshooting

Add custom MCP server is missing

Confirm you are on ChatGPT web, then check plan and role. On Business, ask an admin or owner to create the plugin. On Enterprise or Edu, ask an admin to grant you the permission.

Tools list reads but no writes

Refresh the plugin's tools and inspect workspace action controls. Pro accounts get read/fetch permissions only, so write tools such as create_schedule will not run there.

ChatGPT answers without calling Crontap

Pick the plugin with @ for that message and say not to use browsing or another scheduling tool.

OAuth expires or reconnects repeatedly

Remove and recreate the plugin after checking OAuth metadata. OpenAI notes that refresh-token support and offline_access metadata affect long-lived connectivity.

The schedule runs but the endpoint rejects it

A 401 or 403 in Crontap history is an endpoint-authentication failure. Check request headers on the Crontap schedule page and keep the secret out of the chat.

Next steps

Once the harmless write test passes and you have deleted it, create the weekday daily digest schedule and send one test request from its Crontap schedule page before the first 9am run. Schedule your first job →

Verified against current OpenAI documentation on 2026-11-11, after a live write test on 2026-09-15. Sources: Connect and test your plugin, Connecting custom MCP servers in ChatGPT, and Scheduled tasks in ChatGPT.

FAQ

ChatGPT cron job questions

Can ChatGPT create cron jobs through MCP?
Yes, on a plan with full MCP support. Add Crontap as a custom MCP server from Plugins on ChatGPT web, then ask ChatGPT to create the HTTP schedule and confirm the write tool. Test a harmless write in your account first.
Which ChatGPT plans support MCP write tools?
OpenAI's help article says full MCP support is available for ChatGPT Business and Enterprise/Edu on the web, and that Pro users can connect custom MCP servers with read/fetch permissions. On Business, only admins and owners create custom MCP plugins; Enterprise and Edu admins can grant that through role-based access control.
How should I verify MCP write access?
Create and delete a harmless test schedule before relying on the connection. A live write succeeded in one real ChatGPT account on September 15, 2026, confirming that account and flow rather than every plan or workspace policy.
Are ChatGPT Scheduled Tasks the same as Crontap schedules?
No. ChatGPT scheduled tasks run a ChatGPT prompt on a schedule or event and notify you. Free tasks run at most daily, and hourly or exact times need an eligible paid plan. Crontap sends recurring HTTP requests to endpoints you control, with retries, run history and failure alerts.

From the blog

Read the blog

Guides, patterns and product updates.

Tutorials on scheduling API calls, webhooks and automations, plus deep dives into cron syntax, timezones and reliability.

Product

Introducing Crontap status pages

Publish uptime monitors and heartbeats on a public page at crontap.page, pick a template from Clean to a split-flap departures board, and add incidents, maintenance and a badge.

Product Updates

Introducing AI Integrations

Transform a schedule's HTTP response with a plain-English prompt, return text or JSON, and forward it to Slack, Make, n8n, or your own endpoint. Test on any tier; saving is a Pro feature.

Alternatives

Vercel cron jobs: the Hobby once-per-day limit and how to beat it

Vercel Cron caps Hobby at one run per day, only guarantees timing within the hour, is UTC only, and ties every schedule change to a redeploy. Here is the external cron pattern teams use to ship per-minute, timezone-aware schedules and one dashboard across projects without paying $20/mo per user for Pro.