MCPInstall

crontap-schedule-http-job

by crontapBackend & APIs

Create, update, and verify recurring Crontap HTTP requests with cron or plain English, timezones, headers, and JSON bodies. Use when a user wants to schedule a webhook, API call, or cloud function through MCP or REST.

Installs
879
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/crontap/skills --skill crontap-schedule-http-job
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads crontap-schedule-http-job automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Schedule an HTTP job

Prerequisites

Before using the required tools, check whether they are available. If any are missing, stop and offer the user exactly two choices:

  1. Connect Crontap MCP at https://mcp.crontap.com/mcp. MCP access works on every Crontap tier.
  2. Configure $CRONTAP_CLIENT_ID and $CRONTAP_API_KEY for the raw API. Raw API access requires Ultra.

Do not silently choose a path or continue until the user selects one.

  • Confirm the absolute HTTP or HTTPS endpoint, method, cadence, and IANA timezone.
  • Ask whether the endpoint needs headers, a JSON body, or an idempotency key.
  • Keep credentials out of URLs and logs. Refer to values from a secure store.

Workflow

  1. Preview plain-English cadence and resolve every clarification.
  2. Show the resolved cron, timezone, and next runs to the user.
  3. Create the schedule with exactly one of text or cron.
  4. For changes, identify the existing schedule and send only changed fields.
  5. After execution, inspect retained history and verify the endpoint outcome.

MCP examples

Preview without saving:

{
  "tool": "preview_schedule",
  "arguments": {
    "text": "every weekday at 09:15",
    "timezone": "Europe/Copenhagen"
  }
}

Create a protected JSON request:

{
  "tool": "create_schedule",
  "arguments": {
    "url": "https://app.example.com/api/daily-report",
    "text": "every weekday at 09:15",
    "timezone": "Europe/Copenhagen",
    "method": "POST",
    "headers": {
      "Authorization": "Bearer <secret-from-secure-store>",
      "Content-Type": "application/json"
    },
    "body": {
      "source": "crontap"
    },
    "label": "Daily report"
  }
}

Partially update a schedule:

{
  "tool": "update_schedule",
  "arguments": {
    "scheduleId": "<schedule-id>",
    "cron": "30 9 * * 1-5",
    "timezone": "Europe/Copenhagen"
  }
}

Omitted update fields preserve the existing configuration, including hidden request secrets. An empty headers object replaces and clears headers.

Read recent runs:

{
  "tool": "get_schedule_history",
  "arguments": {
    "scheduleId": "<schedule-id>",
    "limit": 20
  }
}

Use a returned cursor unchanged to request the next page.

REST fallback

Use REST only when MCP is unavailable and the account has Ultra API access. REST uses interval, verb, and data instead of the MCP aliases.

curl --fail-with-body https://api.crontap.com/v1/schedule \
  -X POST \
  -H "ClientId: $CRONTAP_CLIENT_ID" \
  -H "ApiKey: $CRONTAP_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "url": "https://app.example.com/api/daily-report",
    "interval": "30 9 * * 1-5",
    "timezone": "Europe/Copenhagen",
    "verb": "POST",
    "headers": {
      "Authorization": "Bearer <secret-from-secure-store>",
      "Content-Type": "application/json"
    },
    "data": {"source": "crontap"},
    "label": "Daily report"
  }'

Verification

  • Confirm the saved URL, method, cron, timezone, and next runs.
  • Verify the endpoint handles the selected method and returns a success status.
  • Inspect history after the first run for status, duration, timeout, and retry evidence.

Safety and plan limits

  • Preview local-time schedules before creating them, especially around DST.
  • Do not overwrite headers or integrations during an unrelated partial update.
  • Make write endpoints idempotent when retries or overlapping calls are possible.
  • If a plan cap or cadence floor blocks creation, explain the structured four-option upgrade ladder and its smallest viable option.

Troubleshooting

  • A clarification response is not a failure. Ask the returned question, then preview again.
  • A 401 or 403 from the target usually means an expired or malformed endpoint credential.
  • A timeout means Crontap did not receive a response in time. Check endpoint runtime and downstream calls before increasing retries.
  • A 404 from MCP means the schedule ID is stale. List schedules before retrying.

References

FAQ

What does the crontap-schedule-http-job skill do?

Create, update, and verify recurring Crontap HTTP requests with cron or plain English, timezones, headers, and JSON bodies. Use when a user wants to schedule a webhook, API call, or cloud function through MCP or REST.

How do I install crontap-schedule-http-job?

Run npx skills add https://github.com/crontap/skills --skill crontap-schedule-http-job in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/crontap-schedule-http-job/ (personal) or .claude/skills/crontap-schedule-http-job/ (project).

Which AI agents can use crontap-schedule-http-job?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is crontap-schedule-http-job safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains crontap-schedule-http-job?

It is published by crontap in crontap/skills. It has 879 recorded installs.

More from crontap/skills

View all →

crontap-supabase-edge-function-cron

crontap/skills

Schedule a protected Supabase Edge Function or HTTP-facing RPC through Crontap with an external clock and observable delivery. Use when a user needs recurring Supabase work with retries, history, or failure alerts.

Data & Databases887 installs

crontap-heartbeat-for-cron

crontap/skills

Add a Crontap dead-man's-switch heartbeat to an existing recurring job, inspect check-ins, and rotate its secret token safely. Use when a user needs alerts for a cron job that fails explicitly or stops running.

883 installs

crontap-quickstart

crontap/skills

Choose the right Crontap resource, inspect account limits, and verify an IANA timezone before making changes. Use when a user is new to Crontap or needs to decide between schedules, uptime monitors, and heartbeats.

883 installs

crontap-replace-vercel-cron

crontap/skills

Move a Vercel Cron schedule to Crontap while keeping the existing protected HTTP route, timezone intent, and rollback path. Use when a user wants an external scheduler for a Vercel deployment or has outgrown native cron limits.

DevOps & Cloud883 installs

crontap-uptime-monitor

crontap/skills

Create and operate a Crontap uptime monitor, tune its failure threshold, pause it during deployments, and inspect probe evidence. Use when a user wants availability checks and down or recovery alerts for an HTTP endpoint.

882 installs

crontap-retries-and-idempotency

crontap/skills

Configure Crontap retry policy safely and design scheduled endpoints so repeated requests do not duplicate side effects. Use when a user needs reliable delivery, exponential backoff, or help diagnosing duplicate work.

881 installs

Popular backend & apis skills

View category →

find-skills

vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

OfficialBackend & APIs4.1M installs

entra-app-registration

microsoft/azure-skills

Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.

OfficialBackend & APIs566.7K installs

google-agents-cli-adk-code

google/agents-cli

This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).

Backend & APIs514.8K installs

embedded-captions

heygen-com/hyperframes

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

Backend & APIs453.3K installs

entra-agent-id

microsoft/azure-skills

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

OfficialBackend & APIs336.6K installs

neon

neondatabase/agent-skills

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Backend & APIs237.1K installs