Back to MCP

MCP guides · Sep 15, 2026

Schedule a Replit API route with Crontap MCP

Choose between a command-based Scheduled Deployment and an external request to a deployed Replit API, then verify the latter through MCP.
crontap.com / mcp guides
Choose between Replit Scheduled Deployments and Crontap, then connect Crontap MCP and verify a recurring request to an Autoscale API.

As of 2026-11-11, Replit Agent users have two native schedulers: Routines repeat chat work hourly, daily or weekly, and a Scheduled Deployment runs a command on a cron expression, then stops. Neither sends a recurring HTTP request to a route your published app already serves, with retries, run history and failure alerts. Crontap's MCP server fills that gap: Agent creates and checks a hosted Crontap schedule, and Crontap calls your Autoscale route on its own clock without starting a chat.

Choosing the wrong shape makes the setup harder than it needs to be. This guide uses Replit Agent to publish an Autoscale API route, connects Crontap through Replit's custom OAuth MCP flow, and verifies a recurring inventory snapshot. You need a published Replit app and a Crontap account.

Before you start

Choose the scheduling shape

  • Routine: a schedule attached to a Replit chat that repeats work Replit can do in that chat, at most hourly. Routines are on Core, Pro and Enterprise, not Starter, with up to five active per user on Core and 10 on Pro. They cannot schedule publishing.
  • Scheduled Deployment: Replit owns the clock, takes a cron expression and a time zone, and runs a command in the app environment, then stops. It has no public URL and is not managed through Crontap MCP.
  • Crontap plus a deployed API: an Autoscale or Reserved VM deployment serves the URL, while Crontap sends the recurring request. Replit Agent can manage the Crontap resource through MCP.

Step 1

Publish an idempotent API route

Ask Agent to add POST /api/inventory/snapshot. Require X-Inventory-Key to match INVENTORY_KEY, then upsert a snapshot keyed by date. Add the value in Replit Secrets. Publish the app as Autoscale, call the production route with curl, and inspect the request in deployment logs.

Add POST /api/inventory/snapshot to this app. Require X-Inventory-Key to match the INVENTORY_KEY secret, compute today's inventory totals, and upsert one row keyed by snapshot_date. Return JSON with the date and item count. Do not expose the secret in code or logs.

Before publishing, inspect the generated route. Authentication should run before the inventory query, and the database should enforce a unique key on snapshot_date rather than relying only on application logic. Confirm that a successful response contains the snapshot date and item count, while failures use an appropriate non-2xx status. This makes Crontap history useful without returning private row data. In Replit deployment logs, record the route, status, and request ID, but not X-Inventory-Key.

Connect Crontap MCP in Replit

Step 2

Add the custom MCP server

Open Settings → Integrations → Your integrations, then select Add custom → Add personal MCP server (or Add workspace MCP server to share it). Name it Crontap and enter https://mcp.crontap.com/mcp. Leave Advanced settings empty: Crontap needs no custom headers. Choose Test & save, then complete the OAuth flow Replit opens.

Replit Agent MCP server
Crontap
Connected
Authentication
OAuth 2.1

Replit makes the tools available across projects after connection. A confirmation appears when a tool requires it. Review the target project and resource each time instead of treating the global connection as blanket permission.

Step 3

Preview the inventory cadence

In Agent chat, ask Crontap to preview every day at 01:10 in UTC. Check the upcoming dates and keep this turn read-only. The deployed app should not be called during preview.

Using the Crontap MCP server, preview every day at 01:10 in UTC. Show the three upcoming runs and do not create, update, or delete a resource.

Step 4

Create the external HTTP schedule

Copy the published Autoscale URL and append /api/inventory/snapshot. Ask Agent to create a POST schedule using the previewed cadence. Confirm the URL, method, and timezone. Open the returned schedule in Crontap and add the X-Inventory-Key header there.

Create a Crontap schedule named "daily inventory snapshot" that POSTs to https://YOUR-APP.replit.app/api/inventory/snapshot at the cadence we previewed. Show all fields for confirmation before the write. Leave endpoint authentication out of the tool call.

Step 5

Verify the API and schedule

Retrieve the new resource by ID in Agent chat. Perform a test request from Crontap after adding the secret. In Replit's deployment logs, find the matching request and confirm the snapshot table has exactly one row for the date.

Verify it worked in both products

Replit Integrations should show the Crontap connection as saved. Agent should return one schedule ID, and a follow-up read by that ID should show the production replit.app hostname and expected next run. Crontap history should record the test status and duration, Replit deployment logs should show POST /api/inventory/snapshot, and the database should contain the expected totals. Trigger a second test to confirm the upsert does not duplicate the day's snapshot.

If a layer disagrees, check it in order. Reconnect MCP when Integrations does not show the server. Inspect the saved request when Agent can list schedules but the test fails. Inspect application logs and the database write when Crontap records success without a snapshot row. After the first timed run, match the Crontap history timestamp to the Replit deployment log before leaving the schedule active.

Replit Routines, Scheduled Deployments, or Crontap?

QuestionRoutineScheduled DeploymentCrontap schedule
What firesChat work by ReplitA command, then stopsHTTP request to a route
CadenceHourly or less oftenCron plus time zoneCron, any IANA timezone
Calls your routeNoOnly if your command doesYes, directly
Retries, alertsNot an HTTP schedulerNot an HTTP schedulerRetries, email alerts

Last verified 2026-11-11 against Replit docs. Use a Routine for recurring chat work, a Scheduled Deployment for a script that should run in Replit and exit, and Crontap when a published route already does the job.

Troubleshooting

Test & save cannot reach Crontap

Use the complete HTTPS endpoint ending in /mcp and leave the Advanced settings headers empty. Crontap relies on the OAuth flow that Replit opens after testing the server.

Agent cannot see the server

Return to Integrations and verify the saved status. Reconnect if authorization expired. The connection is account-wide, so also confirm you are using the intended Replit account.

The scheduled request hits 404

Do not use a workspace preview URL. Copy the public Autoscale or Reserved VM deployment hostname and verify the route path.

The route returns 401

Compare INVENTORY_KEY in Replit Secrets with the header value stored in Crontap. Keep both values out of chat and logs.

Next steps

If /api/inventory/snapshot already returns the date and item count from curl, create the daily 01:10 UTC schedule, add X-Inventory-Key in Crontap, and run a test. Schedule your first job →

Verified against current official Replit documentation on 2026-11-11. Sources: Replit custom MCP, Replit deployment types, and Replit Routines.

FAQ

Replit scheduling questions

When should I use Replit scheduling instead of Crontap?
Use a Routine for recurring chat work, hourly or less often, on Core, Pro or Enterprise. Use a Scheduled Deployment when a command should run in the app environment on a cron expression and stop. Use Crontap when an Autoscale or Reserved VM deployment already exposes the operation as an HTTP route.
Which Replit deployments can receive Crontap requests?
Use a public API route on an Autoscale or Reserved VM deployment. Copy its production replit.app URL rather than a workspace preview address.
Can Replit Agent connect to Crontap MCP?
Yes. In Settings, Integrations, Your integrations, choose Add custom, then Add personal MCP server. Enter the HTTPS endpoint and select Test & save; Replit walks you through any OAuth flow the server requires.
Where should the Replit endpoint token be stored?
Store the value in Replit Secrets and in the Crontap schedule header. Keep it out of Agent chat, source code, logs, and MCP tool arguments.

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.