Get started free
All integrations

Cronitor integration

Cronitor is a monitoring platform for cron jobs, scheduled tasks, websites, and APIs. The REST API lets you create and manage monitors, environments, notification lists (alert templates), incident issues, and retrieve performance metrics. Authenticate with your account API key (HTTP Basic auth: API key as username, empty password).

17 toolsBasic authAPI docs
Connect CronitorHow integrations work

Common Cronitor use cases

  • audit alert routing
  • list scheduled jobs
  • change cron schedule
  • find monitors by tag
  • audit recent incidents
  • clean up obsolete jobs
  • build performance chart
  • add new cron job tracking
  • set up staging environment
  • set up Slack on-call alerts

What you can do with Cronitor

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Monitor, 8 operations

  • POSTclone_monitor

    Clone an existing Cronitor monitor with a new key.

  • POSTcreate_monitor

    Create a Cronitor monitor (job, check, or heartbeat).

  • DELETEdelete_monitor

    Delete a Cronitor monitor by key.

  • GETget_monitor

    Fetch a single Cronitor monitor by key, optionally with events and invocations.

  • GETlist_monitors

    List all Cronitor monitors with filters and pagination.

  • GETpause_monitor

    Pause or resume a Cronitor monitor for a given number of hours.

  • GETsearch_monitors

    Search Cronitor monitors by free-text query with scope prefixes.

  • PUTupdate_monitor

    Update a Cronitor monitor's editable fields by key.

Environment, 3 operations

  • POSTcreate_environment

    Create a Cronitor environment with optional alerting.

  • DELETEdelete_environment

    Delete a non-default Cronitor environment.

  • GETlist_environments

    List all Cronitor environments with monitor counts and alert flags.

Issue, 3 operations

  • POSTcreate_issue

    Create a Cronitor incident issue and publish to status pages.

  • GETlist_issues

    List Cronitor incident issues with state, severity, and status page filters.

  • PUTupdate_issue

    Update a Cronitor incident issue (state, severity, append update message).

Notification list, 2 operations

  • POSTcreate_notification_list

    Create a Cronitor notification list bundling alert destinations.

  • GETlist_notification_lists

    List Cronitor notification lists (alert templates).

Metric, 1 operation

  • GETget_metrics

    Retrieve time-series Cronitor metrics (duration, success rate, counts).

Cronitor API rate limits

  • 1,000 requests per hour

1000 authenticated requests/hour for metrics endpoints. Other API endpoints share account-level rate limiting; HTTP 429 on excess.

These are the limits Cronitor documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Cronitor documentation for current values.

Use Cronitor from Claude Code, Cursor or Codex

Connect Cronitor in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cronitor operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cronitor

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Cronitor once

    Add your Cronitor connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Cronitor integration FAQ

What can you do with the Cronitor integration?
LiveContext exposes 17 operations on Cronitor, covering monitor, environment, issue and notification list. Common uses include audit alert routing, list scheduled jobs and change cron schedule.
What are the Cronitor API rate limits?
Cronitor documents 1,000 requests per hour. 1000 authenticated requests/hour for metrics endpoints. Other API endpoints share account-level rate limiting; HTTP 429 on excess. Limits are set by Cronitor and can depend on your plan.

Popular integrations

Instagram (Instagram Login)

Instagram API with Instagram Login (graph.instagram.com). Manage a Business/Creator Instagram account…

15 toolsOAuth
Telegram

Messaging platform API for building bots and integrations. Send messages, manage chats and channels, handle…

132 toolsCustom auth
Gmail

Google email service API for sending, receiving, and managing emails. Access messages, threads, labels,…

40 toolsOAuth
YouTube Data API

Google's video platform API for accessing video, channel, playlist, and comment data

52 toolsOAuth
TikTok

Social media platform API for content creators and businesses. Access user info, manage videos, get…

12 toolsOAuth
Twitter / X

Social media platform API for posting, reading, and managing Twitter/X content. Post tweets, read timelines,…

29 toolsOAuth
LinkedIn

Professional networking platform API for managing profiles, connections, and content. Share posts, manage…

49 toolsOAuth
xAI

AI API from xAI (Elon Musk's AI company) powering Grok models. Access state-of-the-art language models with…

11 toolsToken

Browse the whole catalog