Integration

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).

Connect Cronitor How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Cronitor.Built from the 17 Cronitor tools below, on the connection you add once.

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

clone_monitorClone monitorPOSTClone an existing Cronitor monitor with a new key.
create_monitorCreate monitorPOSTCreate a Cronitor monitor (job, check, or heartbeat).
delete_monitorDelete monitorDELETEDelete a Cronitor monitor by key.
get_monitorGet monitorGETFetch a single Cronitor monitor by key, optionally with events and invocations.
list_monitorsList monitorsGETList all Cronitor monitors with filters and pagination.
pause_monitorPause monitorGETPause or resume a Cronitor monitor for a given number of hours.
search_monitorsSearch monitorsGETSearch Cronitor monitors by free-text query with scope prefixes.
update_monitorUpdate monitorPUTUpdate a Cronitor monitor's editable fields by key.

Environment, 3 operations

create_environmentCreate environmentPOSTCreate a Cronitor environment with optional alerting.
delete_environmentDelete environmentDELETEDelete a non-default Cronitor environment.
list_environmentsList environmentsGETList all Cronitor environments with monitor counts and alert flags.

Issue, 3 operations

create_issueCreate issuePOSTCreate a Cronitor incident issue and publish to status pages.
list_issuesList issuesGETList Cronitor incident issues with state, severity, and status page filters.
update_issueUpdate issuePUTUpdate a Cronitor incident issue (state, severity, append update message).

Notification list, 2 operations

create_notification_listCreate notification listPOSTCreate a Cronitor notification list bundling alert destinations.
list_notification_listsList notification listsGETList Cronitor notification lists (alert templates).

Metric, 1 operation

get_metricsGet metricsGETRetrieve 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

Create your workspace
Sign up free. Nothing to install.
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.
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.