Back to MCP

MCP guides · Sep 15, 2026

Create an HTTP cron job from VS Code Copilot Chat

Configure Crontap in VS Code desktop, approve OAuth, and create a recurring endpoint call from Copilot Chat.
crontap.com / mcp guides
Add Crontap MCP to VS Code desktop, create and verify a recurring HTTP request, and avoid GitHub Copilot cloud agent's OAuth limitation.

As of 2026-11-11, VS Code Copilot Chat can schedule agent work natively: Automations in the Agents window run a saved prompt manually, hourly, daily, weekly or on a cron expression on your machine, or daily and weekly in GitHub's cloud. What they run is an agent session. They do not send a recurring HTTP request to your own endpoint with retries, run history and failure alerts. Crontap's MCP server fills that gap by letting Copilot Chat create and manage the request as a hosted Crontap schedule, which keeps firing after VS Code closes and never starts a chat or prompt.

This walkthrough uses VS Code desktop to create and control a recurring request for https://example.com/cache/refresh. You will add Crontap to your MCP configuration, approve OAuth, create the schedule, then pause and resume it from chat. The desktop qualifier is important: GitHub's cloud agent does not currently support OAuth-backed remote MCP servers.

Before you start

Connect VS Code to Crontap MCP

VS Code

.vscode/mcp.json

{
  "servers": {
    "crontap": {
      "type": "http",
      "url": "https://mcp.crontap.com/mcp"
    }
  }
}

Use VS Code desktop. GitHub Copilot cloud agents cannot use OAuth-backed remote MCP servers.

Step 1

Add the Crontap server

Run Chat: Open Customizations, select MCP Servers, then Add Server and choose HTTP with https://mcp.crontap.com/mcp. MCP: Add Server starts the same guided flow. For a personal setup, choose Global, then Copilot Global, which writes ~/.copilot/mcp-config.json with a top-level mcpServers key. The .vscode/mcp.json snippet above still works and is labeled deprecated in the guided flow.

Step 2

Start and authenticate the server

Start Crontap from MCP Servers or run MCP: List Servers. A workspace .vscode/mcp.json inherits Workspace Trust, so in a trusted workspace it starts without a separate MCP trust prompt. Complete browser OAuth and return to VS Code. Crontap should show as running.

VS Code desktop MCP servers
Crontap
Connected
Authentication
OAuth 2.1

Step 3

Preview the daily schedule

In Copilot Chat, ask Crontap to preview “every day at 5am” in America/Chicago without writing. preview_schedule should return an exact cron expression, timezone, and next runs. Confirm they match the intended local mornings.

Step 4

Create the HTTP cron job

Ask Copilot Chat for a POST schedule named daily cache refresh targeting https://example.com/cache/refresh. Review the tool input and approve the write. Crontap returns one active schedule ID and next run.

Step 5

Pause, verify, and resume

Ask Copilot Chat to retrieve the returned ID, pause that exact schedule, and read it again. Confirm the inactive state, then resume the same ID and verify its next run. This exercises workspace MCP writes without creating duplicate schedules.

Ask Copilot Chat with copyable prompts

In a Copilot session, open Chat: Open Customizations > Tools to confirm the Crontap tools are enabled. Local harness sessions use Configure Tools in the chat input instead.

Use only the Crontap MCP tools. Preview "every day at 5am" in America/Chicago without changing a resource. Show the cron expression, timezone, and three upcoming runs.
Create a POST schedule named "daily cache refresh" for https://example.com/cache/refresh using the cadence we previewed. Show the complete non-secret input and wait for my approval before calling create_schedule.
List my Crontap schedules, retrieve "daily cache refresh" by ID, pause that exact ID, confirm it is inactive, then ask before resuming it. After approval, resume it and report the next run.

Verify the VS Code cron job worked

The first checkpoint is client status. Run MCP: List Servers, choose Crontap, and verify that it is running. The second checkpoint is the resource. Make Copilot Chat retrieve the schedule ID returned by the create call, then inspect the pause and resume tool results.

Open Crontap and compare the same URL, method, timezone, cadence, and active state. After the first fire, ask Copilot Chat for schedule history. Match its timestamp and HTTP result to the route's own logs. A 500 in Crontap history means the clock fired and your route failed. A missing history item after the expected time points toward status, cadence, or timezone.

If you share .vscode/mcp.json, teammates get the server definition but still authenticate as themselves. That is useful for consistent tooling without copying credentials. Review every write approval and retrieve the target resource before pause, update, or delete operations.

VS Code Automations or a Crontap schedule?

Automations and Crontap answer different questions. An automation starts an agent run from a saved prompt. A Crontap schedule sends one HTTP request to an endpoint you already deployed, then records the result.

QuestionVS Code AutomationsCrontap schedule
What firesAn agent session from a saved promptAn HTTP request to your endpoint
CadenceLocal: hourly to cron. Cloud: daily or weeklyCron or presets, per-schedule zone
TimezoneLocal: your machine. Cloud: UTCAny IANA timezone
Needs your computer awakeLocal: yes. Cloud: noNo, Crontap hosts the clock
Can use Crontap MCPLocal: yes. Cloud: no OAuth serversNot needed, it is the schedule
Retries and alertsNot an HTTP schedulerPer-schedule retries, email alerts

Last verified 2026-11-11 against VS Code and GitHub docs. Cloud automations are in preview, run at :00, :15, :30 or :45, and need VS Code 1.144 or later, a private repository, and Copilot Pro, Pro+, Max, Business or Enterprise. They can only use MCP servers from repository MCP settings, which don't support OAuth, so they cannot use OAuth MCP servers such as Crontap.

Use an automation when the work is reasoning over the repository. Use Crontap when a deployed route needs a dependable clock with history, and manage it from Copilot Chat when that is convenient.

Why this guide is desktop-only

VS Code desktop supports remote HTTP MCP servers and OAuth. GitHub's repository-level MCP configuration is used by Copilot cloud agent and Copilot code review, and GitHub currently states that those surfaces do not support remote MCP servers that use OAuth. Do not paste this configuration into Repository Settings > Copilot > MCP servers and expect the cloud agent to authenticate. It is an authentication-surface limitation, not a missing tool allowlist.

If you want another local surface, use a supported desktop client such as Cursor, Claude Code, or Codex. Crontap still runs the saved HTTP schedule after VS Code closes because the schedule lives in Crontap. Only the interactive management step depends on the desktop client.

Troubleshooting

VS Code does not discover .vscode/mcp.json

Confirm the root key is servers, not mcpServers, and that the entry includes "type": "http". Copilot Global's ~/.copilot/mcp-config.json uses mcpServers instead, so do not copy one file into the other unchanged. Run MCP: List Servers to check what VS Code loaded.

The server will not start in this workspace

A workspace .vscode/mcp.json follows Workspace Trust, and restricted mode keeps it from starting. Review the file, then trust the workspace. MCP: Reset Trust only resets separate trust decisions for non-workspace sources such as Copilot Global. The production URL must be exactly https://mcp.crontap.com/mcp.

OAuth completes but the server shows an error

Use MCP: List Servers > Crontap > Show Output, or the server's ... menu in MCP Servers. Check proxy, callback, and tool-discovery errors.

Copilot Chat does not call a Crontap tool

In a Copilot session, open Chat: Open Customizations > Tools and enable the required tool. Local harness sessions use Configure Tools in the chat input. Mention Crontap and the tool action explicitly, and separate preview from create.

The configuration works locally but not in GitHub cloud agent

GitHub's cloud agent cannot complete the OAuth flow required by Crontap. Keep this workflow in VS Code desktop, where the browser sign-in is supported.

Next steps

If your cache refresh route is already deployed, create the daily 5am America/Chicago schedule from Copilot Chat with the prompts above, then run a test from its Crontap schedule page before the first fire. Schedule your first job →

Verified with VS Code desktop MCP and automations documentation and GitHub Copilot cloud-agent restrictions on 2026-11-11. Sources: VS Code MCP servers, VS Code automations, and GitHub Copilot cloud MCP configuration.

FAQ

VS Code Copilot cron job questions

Can VS Code Copilot Chat create cron jobs?
VS Code desktop can use Crontap MCP tools to create and manage recurring HTTP requests. Crontap schedules the endpoint, not Copilot Chat itself. VS Code's own Automations schedule agent sessions from a saved prompt, not HTTP requests to your endpoint.
Where do I put the VS Code MCP configuration?
Run Chat: Open Customizations, select MCP Servers, then Add Server. For a personal setup choose Global, then Copilot Global, which writes ~/.copilot/mcp-config.json. A workspace .vscode/mcp.json with a servers key still works but is labeled deprecated in the guided flow.
Can GitHub Copilot cloud agent connect to Crontap MCP?
Not through the current Crontap OAuth flow. GitHub documents that Copilot cloud agent and code review do not support remote MCP servers that use OAuth.
How do I inspect VS Code MCP errors?
Run MCP: List Servers, select Crontap, and choose Show Output. You can also open Chat: Open Customizations, select MCP Servers, and use the server's ... menu to choose Show Output.

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.