Saltar al contenido
Marketplace

crontap-quickstart

de crontap

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.

Resumen

SKILL.mdLeída en 31e242b

Crontap quickstart

Crontap provides three related resources:

  • A schedule sends an HTTP request on a cron or plain-English cadence.
  • An uptime monitor probes a URL and records availability.
  • A heartbeat expects an existing job to ping after it runs.

MCP lets the current agent manage these resources. Crontap owns HTTP scheduling and observability, not the lifecycle of the MCP client.

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.

  • Connect the remote MCP server at https://mcp.crontap.com/mcp and complete OAuth in the target Crontap account.
  • Know the intended endpoint, local timezone, and desired failure signal.
  • Treat endpoint authorization values and heartbeat ping URLs as secrets.

Workflow

  1. Call get_account_usage before creating resources when capacity is uncertain.
  2. Compare usage.combined with caps.combined and inspect feature flags.
  3. Choose a schedule for outbound execution, a monitor for endpoint availability, or a heartbeat for missed check-ins.
  4. Call list_timezones when the exact IANA timezone is uncertain.
  5. Hand off to the focused skill for creation and verification.

MCP examples

Inspect the active tier, usage, caps, features, and plan options:

{
  "tool": "get_account_usage",
  "arguments": {}
}

Find accepted timezone names:

{
  "tool": "list_timezones",
  "arguments": {
    "query": "Copenhagen"
  }
}

Use the exact returned timezone, such as Europe/Copenhagen. Do not substitute a fixed UTC offset for a local-time business schedule.

REST fallback

The public API is a fallback only for accounts with Ultra API access. MCP is not Ultra-only.

curl --fail-with-body https://api.crontap.com/v1/account \
  -H "ClientId: $CRONTAP_CLIENT_ID" \
  -H "ApiKey: $CRONTAP_API_KEY"

Keep both values in environment variables or a secret manager. Never put them in a repository, agent transcript, URL, or example output.

Safety and plan limits

  • Starter, Pro, and Ultra use one combined cap for schedules, monitors, and heartbeats. Some resource-specific caps and cadence floors also apply.
  • Treat the returned account object as authoritative. Do not hard-code prices or assume a feature from the tier name.
  • If a tool returns a structured plan-limit error, present its ordered four-option ladder and identify the smallest viable option. Do not invent a fifth option or hide the all-plans URL.
  • Confirm the target account before any write operation.

Troubleshooting

  • If OAuth fails, reconnect the MCP server in the client and retry once.
  • If a timezone search returns no match, try a city or region substring.
  • If REST returns API_REQUIRES_ULTRA, continue through MCP or let the user choose an Ultra option.
  • If MAX_ITEMS_REACHED appears, do not retry the same create call unchanged.

References

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add crontap/skills --skill crontap-quickstart

Más de crontap

  • crontap-ai-built-appscrontapAdd recurring HTTP work and liveness monitoring to apps built with Lovable, Bolt, Replit, or v0 by exposing a protected endpoint. Use when a user wants an AI-built app to perform durable scheduled work after deployment.1 instalaciones en skills.sh0
  • crontap-debug-failed-runscrontapDiagnose failed Crontap schedule runs from saved configuration and retained execution history, separating scheduler, network, timeout, and endpoint failures. Use when a scheduled HTTP job is late, failing, or unexpectedly unauthorized.1 instalaciones en skills.sh0
  • crontap-heartbeat-for-croncrontapAdd 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.1 instalaciones en skills.sh0
  • crontap-natural-language-schedulescrontapTranslate plain-English timing into a reviewed cron expression and concrete next runs without creating a schedule. Use when a user describes a recurring cadence in words or when timezone and calendar wording is ambiguous.1 instalaciones en skills.sh0
  • crontap-recurring-agent-endpointcrontapSchedule an HTTP endpoint that a deployed application uses to start its own agent workflow, then monitor completion with a heartbeat. Use when a user has an application-owned agent runtime that needs a durable external clock.1 instalaciones en skills.sh0
Todas las skills de crontap