Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.
Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://cronjob.agentasy.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.agentasy-cronjob https://cronjob.agentasy.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.agentasy-cronjob": { "command": "npx", "args": [ "-y", "mcp-remote", "https://cronjob.agentasy.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
README is not crawled yet. No repository on file.
Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.
{ "mcpServers": { "ai.agentasy-cronjob": { "url": "https://cronjob.agentasy.ai/mcp", "headers": {} } }}15 tools
FAQ
| Step 3. Poll verification state with the setup_token. The first call after the webhook is verified returns hmac_secret (signs triggers) and management_token (manages the job) — SHOWN ONCE, store them now; later calls say credentials: "already_issued". (REST: GET /v1/jobs/{id}/verification) |
| retry_challenge | Re-send a fresh url_verification challenge to your webhook (at most 5 re-sends (6 challenges in total), at least 60 s apart). The previous challenge stops working. (REST: POST /v1/jobs/{id}/verification/retry) |
| list_jobs | Status of every job you hold a management token for. There are no accounts, so pass each {job_id, management_token} pair (up to 20); a pair without management_token uses the Authorization header. (REST: GET /v1/jobs/{id} (once per job)) |
| get_job | Settings, status, next_run_at, run_count and credential prefixes of one job (webhook path masked). (REST: GET /v1/jobs/{id}) |
| update_job | Change a job in place: signature_in_body (true = triggers also carry cronjob_signature in the JSON body, for platforms that drop the X-Cronjob-* headers; applies from the next attempt sent) and/or max_runs. Raising max_runs on a job completed with max_runs_reached reactivates it (next run = next occ |
| pause_job | Stop triggering (idempotent). Schedule points while paused are not made up later. (REST: POST /v1/jobs/{id}/pause) |
| resume_job | Resume a paused or disabled job from its next schedule point; resets consecutive_failures. (REST: POST /v1/jobs/{id}/resume) |
| delete_job | Stop the job forever and revoke all its credentials. Cannot be undone. (REST: DELETE /v1/jobs/{id}) |
| get_deliveries | Trigger log, newest first: scheduled_at, first attempt time, delay, attempts, status and last response code of each run. since/until (ISO 8601) filter scheduled_at; page with next_cursor. (REST: GET /v1/jobs/{id}/runs) |
| get_run | One run and each delivery attempt: sent_at, response status, duration, error and next retry. (REST: GET /v1/jobs/{id}/runs/{run_id}) |
| get_stats | On-time rate, p50/p95 first-attempt delay and success rate over a window (default 24h). (REST: GET /v1/jobs/{id}/stats) |
| rotate_secret | New hmac_secret (SHOWN ONCE, store it now). Until previous.expires_at (grace_sec, default 24 h) triggers carry two v1= signatures, new first. (REST: POST /v1/jobs/{id}/rotate-secret) |
| rotate_token | New management_token (SHOWN ONCE, store it now). The old one stops working after grace_sec (default 0 = immediately). (REST: POST /v1/jobs/{id}/rotate-token) |
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Agent Cronjob is reached over HTTP.
Last checked 2026-11-13. Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.