Back to MCP

MCP guides · Sep 15, 2026

Devin cron jobs: manage an API with Crontap MCP

Connect Devin Local to Crontap, approve a recurring webhook schedule, and verify the result from Devin Desktop and your service logs.
crontap.com / mcp guides
Connect Devin Local to Crontap over Streamable HTTP, complete browser OAuth, approve MCP tools, and verify a recurring request to a deployed API.

As of 2026-11-11, Devin can schedule agent work natively: Devin Cloud Automations with a Schedule trigger start a Devin session every hour, day or week, once, or on a custom RRULE, in a time zone you pick. That runs Devin, not your endpoint. Devin has no built-in way to send a recurring HTTP request to your own API with retries, run history and failure alerts. Crontap's MCP server fills that gap: Devin Local creates and checks a hosted Crontap schedule while you work, and Crontap sends the request on its own clock without starting Devin.

You used Devin Local to build and deploy POST /api/docs/snapshot, which refreshes a customer-facing API documentation snapshot. The endpoint now needs to run at 07:15 every weekday in the service team's timezone. This guide connects the shared Devin Local and Devin CLI MCP harness to Crontap, completes browser authorization, and creates the recurring request with explicit approval. You need a Crontap account, current Devin Desktop or Devin CLI, and an idempotent public HTTPS endpoint.

Before you start

  • Run the endpoint manually and verify that repeating it does not duplicate data.
  • Choose an IANA timezone such as Europe/Amsterdam, not a fixed UTC offset.
  • Keep endpoint credentials out of prompts and MCP arguments. Add the secret in the Crontap UI after the schedule exists.
  • Use Devin Local in Devin Desktop. It is the current primary local agent and shares its agent harness with Devin CLI.
  • Verified against Devin MCP configuration, Devin Local, the Devin Desktop FAQ, and Devin Automations on 2026-11-11.

Connect Devin Local to Crontap

Devin Local

devin mcp add crontap https://mcp.crontap.com/mcp
devin mcp login crontap

Devin Local shares this MCP configuration and OAuth flow with Devin CLI.

The first command adds a URL-based MCP server. Devin infers HTTP and tries Streamable HTTP first. Current releases save it to .devin/mcp_config.local.json by default, which is gitignored. Use --scope project for .devin/mcp_config.json or --scope user for ~/.config/devin/mcp_config.json on macOS and Linux.

Step 1

Add the Crontap server

Run devin mcp add crontap https://mcp.crontap.com/mcp from your project. Then run devin mcp get crontap and confirm the exact URL. You do not need to set transport because Devin treats a URL as Streamable HTTP by default.

Step 2

Authorize in your browser

Run devin mcp login crontap. Devin opens a browser window for OAuth, stores the resulting tokens locally, and refreshes them automatically. Return to Devin Desktop after authorization and confirm that Crontap no longer shows Needs authentication.

Devin Local MCP connection
Crontap
Connected
Authentication
OAuth 2.1

Step 3

Preview the weekday cadence

Ask Devin Local to preview 07:15 on weekdays in Europe/Amsterdam. Keep this first request read-only. Check the three upcoming occurrences, especially around daylight-saving changes, before allowing any schedule creation.

Step 4

Review and create one schedule

Ask for one active POST schedule targeting the deployed snapshot route. Devin Local prompts before MCP tool calls by default. Review the tool name, URL, method, timezone, and cadence on the permission card, then approve only the intended call. A session grant can cover later calls, while permanent allow rules belong in Devin's permissions configuration.

Step 5

Add authentication and verify

Retrieve the new schedule by the exact ID returned from creation. Open that schedule in Crontap, add Authorization or another endpoint secret in the Crontap UI, and perform a test request. Compare Crontap history with the deployed service logs and the snapshot's generated timestamp.

Copyable Devin Local prompts

Use the connected Crontap MCP server. Preview a schedule for 07:15 every weekday in Europe/Amsterdam and show the three upcoming occurrences. Do not create or update anything.
Create one active schedule named "weekday API docs snapshot" that POSTs to https://docs-api.example.com/api/docs/snapshot using the cadence we previewed. Show the final URL, method, timezone, and cadence before the create tool. Do not add authentication headers or secret values.
Retrieve the schedule using the exact ID from the create result. Report its active state, URL, method, timezone, next run, and latest history entry. Do not update or delete it.

Verify the schedule end to end

Run devin mcp list to confirm that crontap is configured. If authorization has expired, Devin reports an auth-required state. In Devin Desktop, the MCP server detail can show Needs authentication and an Authenticate action. At the command line, devin mcp logout crontap followed by devin mcp login crontap clears stale credentials and repeats the browser flow.

The create result should contain one schedule ID. The next read must use that ID rather than selecting a similarly named resource. In Crontap, confirm the production hostname, POST method, weekday cadence, and Europe/Amsterdam timezone. Add the endpoint credential there and run a test.

Finally, inspect the application result. Find the matching request in service logs and confirm that the documentation snapshot timestamp advanced. HTTP success alone does not prove that the application completed useful work.

Devin Local workflow or Crontap schedule?

Devin Local is the interactive MCP client. It helps you create and inspect a durable Crontap resource, but Crontap does not reopen Devin or start a prompt later. Closing Devin Desktop does not stop a saved Crontap schedule.

Devin's native scheduling lives in Devin Cloud. An automation with a Schedule trigger starts a Devin session; Scheduled Sessions are now documented as a legacy feature. On the local side, the Devin Desktop FAQ says Devin Local replaces memories and workflows with rules and skills. Skills give the agent reusable instructions, but neither is a hosted HTTP clock.

QuestionDevin AutomationsCrontap schedule
What firesA Devin session doing agent workAn HTTP request to your endpoint
CadenceHourly, daily, weekly, once, RRULECron or presets
TimezonePer schedule, follows DSTPer schedule, any IANA timezone
Run recordThe Devin sessionStatus, code, duration, error
Retries and alertsNot an HTTP schedulerPer-schedule retries, email alerts

Last verified 2026-11-11 against Devin docs. Use an automation when the recurring work needs Devin to reason or change code. Use Crontap when an existing endpoint needs a recurring request, a deployment platform's native scheduler when code must execute inside that platform, and a heartbeat when another scheduler already runs the job.

Troubleshooting

The server is missing after devin mcp add

Run the command from the intended project and inspect devin mcp get crontap. The default local file is .devin/mcp_config.local.json. Project and user scopes use different files, and a higher-priority definition with the same name wins.

OAuth does not open or returns Auth required

Run devin mcp login crontap directly. If credentials are stale, log out and back in. Corporate browser controls must allow the temporary loopback redirect used by the OAuth flow.

Devin Local cannot see Crontap tools

Confirm the server is enabled with devin mcp list. Enterprise teams can disable MCP, require an approved registry, or restrict servers with an allowlist. Ask an admin to permit the exact Crontap URL.

Every MCP call asks for approval

That is Devin Local's documented default. Approve the specific tool or all tools from that server for the current session. Only add patterns such as mcp__crontap__* to a permanent allow list after reviewing their scope.

The test request returns 401 or 403

The MCP connection succeeded, but the deployed endpoint rejected Crontap's request. Compare the credential configured in the Crontap UI with the deployment secret and confirm the header name. Do not paste its value into Devin chat.

Next steps

If the snapshot route already answers a manual POST, create the weekday schedule, add its credential in Crontap, and run a test before the first 07:15 fire. Schedule your first job →

Verified against current official Devin Desktop, Devin Local, Devin CLI, and Devin Automations documentation on 2026-11-11. Sources: Devin MCP configuration, Devin Local agent, Devin Desktop FAQ, and Devin Automations.

FAQ

Devin Local cron job questions

Does Devin Local support remote Streamable HTTP MCP servers?
Yes. Devin CLI treats a URL as HTTP and uses Streamable HTTP by default. Devin Local shares the same agent harness and MCP configuration.
Where does Devin store MCP server configuration?
Current releases default devin mcp add to .devin/mcp_config.local.json. Project scope uses .devin/mcp_config.json, and user scope uses ~/.config/devin/mcp_config.json on macOS and Linux.
How does Devin authenticate with Crontap?
Run devin mcp login crontap, or use the server for the first time. Devin opens a browser authorization flow, stores the OAuth tokens locally, and refreshes them automatically.
Does Crontap run Devin Local on a schedule?
No. Devin Local manages the schedule through MCP while you work. Crontap independently sends the saved HTTP request on its configured cadence. Recurring Devin sessions are a separate Devin Cloud feature: Automations with a Schedule trigger.

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.