Cronitor (Cron Monitoring) Connector for AI agents.

44 live capabilities

Manage cron jobs and uptime monitoring from your AI client.

Live agent request Cronitor (Cron Monitoring) / Connector

Waiting for input…

AI Agent

Why people use Cronitor (Cron Monitoring)

Cronitor for SRE Uptime Monitoring

With this Connector, you just tell your agent to silence alerts for the next hour. It handles the API calls to create_maintenance_window for you, so you can stay focused on the deployment.

What Vinkius changes

That it turns your monitoring dashboard into a conversational interface for your AI.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

Real-world use case 01

Outage Management

An SRE notices a spike in errors.
Real-world use case 02

Deployment Window

A developer is about to run a script.
Real-world use case 03

Performance Audit

A product manager wants to know site speed.

Complete set · 44capabilities

The complete Cronitor (Cron Monitoring) capability set.

These are the exact actions your AI can choose when you ask it to work with Cronitor (Cron Monitoring).

Capability set01 / 11

01—04

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

01 Capability
Create api key
Generate a new API key for your Cronitor account. This is useful for setting up secure access for your AI agent.
02 Capability
Create status page component
Add a new component to an existing status page. Use this to build out specific sections of your public status updates.
03 Capability
Create environment
Set up a new environment for your monitoring. This helps you organize monitors by production, staging, or dev stacks.
04 Capability
Create group
Create a new monitor group. Use this to batch monitors by service or team for easier management.

Capability set02 / 11

05—08

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

05 Capability
Create issue
Log a new issue in your system. This lets you track specific incidents as they occur.
06 Capability
Create maintenance window
Schedule a maintenance window. This tells the system to silence alerts during planned work periods.
07 Capability
Create notification
Create a notification list. This defines who gets alerted when your monitors go down.
08 Capability
Create site
Create a RUM site. Use this to start tracking real user monitoring data for your web applications.

Capability set03 / 11

09—12

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

09 Capability
Create status page
Create a status page. This builds a public-facing page to communicate uptime to your customers.
10 Capability
Delete api key
Delete an API key. Use this to remove old or compromised keys from your account.
11 Capability
Delete group
Delete a monitor group. Use this to clean up old monitor groupings in your account.
12 Capability
Delete monitor
Delete a monitor. Use this to stop tracking a specific cron job or heartbeat.

Capability set04 / 11

13—16

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

13 Capability
Delete site
Delete RUM sites. Use this to remove specific site analytics from your dashboard.
14 Capability
Delete status page
Delete status pages. Use this to remove public status pages from your account.
15 Capability
Get aggregates
Retrieve rolled-up aggregates. Use this to see summarized performance data over time.
16 Capability
Get metrics
Retrieve performance metrics. Use this to see specific data points like latency and success rates.

Capability set05 / 11

17—20

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

17 Capability
Get monitor
Retrieve a specific monitor. Use this to see the full details of a single health check.
18 Capability
Get site errors
Get site errors. Use this to identify specific issues happening on your RUM sites.
19 Capability
List api keys
List API keys. Use this to audit all active keys in your Cronitor account.
20 Capability
List status page components
List status page components. Use this to see all parts of your public status pages.

Capability set06 / 11

21—24

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

21 Capability
List environments
List environments. Use this to see all the different stacks you are monitoring.
22 Capability
List groups
List monitor groups. Use this to see how your monitors are organized.
23 Capability
List issues
List issues and incidents. Use this to see a history of problems in your infrastructure.
24 Capability
List monitors
List or search monitors. Use this to find specific health checks across your whole stack.

Capability set07 / 11

25—28

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

25 Capability
List notifications
List notification lists. Use this to see who is currently receiving alerts.
26 Capability
List sites
List RUM sites. Use this to see all the websites you are tracking for analytics.
27 Capability
List status pages
List status pages. Use this to see all your public status pages.
28 Capability
Pause group
Bulk pause or resume a group of monitors. Use this to silence alerts for an entire stack at once.

Capability set08 / 11

29—32

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

29 Capability
Update environment
Update an environment. Use this to change the configuration of a specific monitoring stack.
30 Capability
Update issue
Update an issue state. Use this to move an incident from 'Open' to 'Resolved' or 'In Progress'.
31 Capability
Update monitors
Create or update monitors in bulk. Use this to apply changes to many monitors at once.
32 Capability
Update notification
Update a notification list. Use this to change who gets alerted for your monitors.

Capability set09 / 11

33—36

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

33 Capability
Update status page
Update status pages. Use this to change the content of your public status pages.
34 Capability
Create monitor
Create a new monitor. Use this to start tracking a new cron job, heartbeat, or website.
35 Capability
Delete status page component
Delete status page components. Use this to remove specific sections from your public status pages.
36 Capability
Pause monitor
Pause or resume a monitor. Use this to silence alerts for a single specific heartbeat or job.

Capability set10 / 11

37—40

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

37 Capability
Query site analytics
Query site analytics. Use this to pull performance data from your RUM sites.
38 Capability
Send telemetry
Send telemetry events. Use this to send pings and metrics from your application to Cronitor.
39 Capability
Update api key
Update an API key. Use this to modify the settings of an existing key.
40 Capability
Update status page component
Update status page components. Use this to modify specific parts of your public status pages.

Capability set11 / 11

41—44

4 capabilities in this set.

Part of 44 available through Cronitor (Cron Monitoring).

41 Capability
Update group
Update a monitor group. Use this to change how your monitors are organized.
42 Capability
Update site
Update RUM sites. Use this to modify the settings for your site analytics.
43 Capability
Bulk issues
Perform bulk actions on issues. Use this to update multiple incidents in a single command.
44 Capability
Clone monitor
Clone an existing monitor. Use this to quickly replicate a health check for a new service.

Set up in minutes

One URL. Then ask Cronitor (Cron Monitoring) to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Cronitor (Cron Monitoring) from the conversation.

Choose your client

Live preview

Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp

Step 01

Open Connectors

In Claude Web or Claude Desktop, open Settings and choose Connectors.
Step 02

Add the URL

Choose Add custom connector, name it Cronitor (Cron Monitoring), and paste the URL above.
Step 03

Turn it on in chat

Select +, open Connectors, and enable Cronitor (Cron Monitoring) for the conversation.

ChatGPT · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp

Step 01

Open MCP settings

On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
Step 02

Add the URL

Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Cronitor (Cron Monitoring) URL.
Step 03

Save and start

Save the connection and enable Cronitor (Cron Monitoring) in your conversation. Desktop may ask you to restart once.

Cursor · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "cronitor-cron-monitoring": {
      "url": "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"
    }
  }
}

Step 01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Step 02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
Step 03

Save the file

Cursor will automatically detect the new Connector
Step 04

Start using Cronitor (Cron Monitoring)

Open Agent mode in chat and ask: "Using Cronitor (Cron Monitoring), help me...". 44 tools available

VS Code Copilot · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "cronitor-cron-monitoring": {
      "url": "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"
    }
  }
}

Step 01

Create MCP config

Create a .vscode/mcp.json file in your project root
Step 02

Add the server config

Paste the JSON configuration above
Step 03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Step 04

Start using Cronitor (Cron Monitoring)

Ask Copilot: "Using Cronitor (Cron Monitoring), help me...". 44 tools available

Windsurf · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "cronitor-cron-monitoring": {
      "url": "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"
    }
  }
}

Step 01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Step 02

Add the server

Paste the JSON configuration above into mcp_config.json
Step 03

Save and reload

Windsurf will detect the new server automatically
Step 04

Start using Cronitor (Cron Monitoring)

Open Cascade and ask: "Using Cronitor (Cron Monitoring), help me...". 44 tools available

Cline · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "cronitor-cron-monitoring": {
      "url": "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"
    }
  }
}

Step 01

Open Cline MCP Settings

Click the Connectors icon in the Cline sidebar panel
Step 02

Add remote server

Click "Add Connector" and paste the configuration above
Step 03

Enable the server

Toggle the server switch to ON
Step 04

Start using Cronitor (Cron Monitoring)

Ask Cline: "Using Cronitor (Cron Monitoring), help me...". 44 tools available

Claude Code · Terminal command

Official guide ↗

Advanced setup

claude mcp add cronitor-cron-monitoring --transport http "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"

Step 01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
Step 02

Add the Connector

Run the command above in your terminal
Step 03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
Step 04

Start using Cronitor (Cron Monitoring)

Ask Claude: "Using Cronitor (Cron Monitoring), show me...". 44 tools are ready

Where the request belongs

Work Cronitor can move forward.

Built around the request

The ops engineer who's tired of clicking through dashboards at 2am to see if a cron job failed, or the developer who needs to verify background tasks without leaving their code editor.

01

DevOps Engineer

Checks monitor statuses and silences alerts during maintenance without leaving the terminal.

02

Backend Developer

Verifies cron job performance and sends telemetry pings directly from the code editor.

03

SRE & Ops Lead

Manages status pages and tracks incident history across multiple production environments.

Build the capability set

Each Connector adds new actions and data without changing how you work.

Browse Connectors

01 13 capabilities

Healthchecks.io

Monitor cron jobs and background tasks via Healthchecks.io. list checks, track pings, and manage alerts directly from any AI agent.

02 10 capabilities

UptimeRobot

Monitor and manage your website uptime seamlessly. List, create, and resolve monitor alerts directly from your AI agent, 24/7.

03 10 capabilities

Honeybadger (Error Tracking)

Monitor app exceptions and uptime via Honeybadger. list projects, resolve faults, and track deployments.

04 11 capabilities

HetrixTools

Automate uptime monitoring and blacklist checks via HetrixTools. monitor servers, websites, and IP reputation directly from any AI agent.

05 8 capabilities

Checkmk

Manage IT infrastructure monitoring via Checkmk. track hosts, monitor services, and activate changes directly from any AI agent.

06 12 capabilities

Uptime.com

Monitor website and API uptime from 30+ global locations with instant alerts when downtime hits any of your services.

Bring your own AI

Change the model, client or framework. Keep Cronitor connected.

Before you connect

Questions about Cronitor.

The practical details behind the request, access and result.

Can I use Cronitor MCP to silence alerts?

Yes, you can ask your agent to create_maintenance_window for specific monitors or groups. This stops notifications during planned work so you don't get paged unnecessarily.

Does Cronitor MCP support heartbeats?

Yes, your agent can send_telemetry to report heartbeats. This is great for checking if a background worker is still alive.

Can my agent update our public status page?

Absolutely. You can use the Connector to update_status_page or create_status_page_component to keep your users informed during an incident.

How do I check my cron job performance?

Just ask your agent to get_metrics for a specific monitor. It will pull the latest latency and success data directly from Cronitor.

Can I manage multiple environments with Cronitor MCP?

Yes, you can list_environments and use the Connector to create or update monitors across different stacks in one conversation.

Is it possible to bulk update my monitors?

Yes, the update_monitors capability allows your agent to modify multiple monitors at once, which is much faster than doing it one by one.

How can I manually signal that a job has finished successfully?

You can use the send_telemetry capability. Provide the monitor_key and set the state to 'complete'. This will immediately update Cronitor with the job's success status.

Is it possible to silence alerts for a specific monitor during maintenance?

Yes! Use the pause_monitor capability with the monitor_key and the number of hours you want to pause it. Alternatively, use create_maintenance_window for broader scheduling.

How do I check for recent errors on my monitored websites?

Use the get_site_errors capability. It retrieves the most recent error logs and failure details for a specific site monitor, helping you debug downtime quickly.

One connection away

Give your agent a direct line to Cronitor.

Connect Cronitor once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available