Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaredhobbs avatar

Cronalert MCP

  • Updated July 1, 2026
  • jaredhobbs/cronalert-mcp

CronAlert MCP is a MCP server that manages uptime monitors, check results, and incidents in CronAlert.

About

CronAlert MCP lets AI agents manage external uptime monitoring: defining monitors, inspecting check outcomes, and tracking incidents tied to CronAlert’s service. developers who already rely on CronAlert to watch cron schedules or HTTP endpoints can stay inside Claude Code or Cursor when they need to add a monitor after a deploy, verify recent failures, or triage an open incident. The server is a monitoring integration, not an on-host log shipper or APM suite—you still need a CronAlert account and appropriate API credentials configured per the project README. Complexity is beginner to intermediate depending on how many monitors and environments you operate. It shines when your stack is small but you want conversational ops instead of tab-hopping; skip it if you use a different uptime vendor or have not shipped anything worth monitoring yet.

  • Manage CronAlert uptime monitors from any MCP-compatible client
  • Read check results and incident history without opening the CronAlert dashboard
  • npm stdio package cronalert-mcp (v1.0.6)
  • Pairs with solo builders who run cron jobs and HTTP endpoints needing external pings
  • Agent-friendly ops workflow for small teams without a full NOC toolchain

Cronalert MCP by the numbers

  • Data as of Aug 10, 2026 (Skillselion catalog sync)
terminal
claude mcp add cronalert-mcp -- npx -y cronalert-mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Packagecronalert-mcp
TransportSTDIO
AuthNone
Last updatedJuly 1, 2026
Repositoryjaredhobbs/cronalert-mcp

What it does

Create and review CronAlert uptime monitors, check history, and incidents from your agent while you run production URLs and cron jobs.

Who is it for?

SaaS and cron-heavy side projects already on CronAlert that want MCP-driven uptime ops.

Skip if: Skip if you're on Datadog, Better Stack, or self-hosted Prometheus only, or pre-launch builds with nothing to monitor.

What you get

You can configure monitors and pull check and incident context into the same agent thread that fixes the outage.

  • Monitors created or updated through agent sessions
  • Check result snapshots available in chat for debugging
  • Incident context pulled for faster solo triage

By the numbers

  • Package version 1.0.6 (cronalert-mcp)
  • stdio npm transport
  • Tool surface: monitors, check results, and incidents per description
README.md

cronalert-mcp

MCP server for CronAlert uptime monitoring. Manage your monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.

Quick Start

1. Get your API key

Sign up at cronalert.com and create an API key in Settings > API Keys.

2. Add to your MCP client

Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "cronalert": {
      "command": "npx",
      "args": ["-y", "cronalert-mcp"],
      "env": {
        "CRONALERT_API_KEY": "ca_your_api_key_here"
      }
    }
  }
}

Claude Code — run:

claude mcp add cronalert -e CRONALERT_API_KEY=ca_your_key -- npx -y cronalert-mcp

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "cronalert": {
      "command": "npx",
      "args": ["-y", "cronalert-mcp"],
      "env": {
        "CRONALERT_API_KEY": "ca_your_api_key_here"
      }
    }
  }
}

Remote server (no install needed) — connect any MCP client to:

https://cronalert.com/mcp

Authenticate with Authorization: Bearer ca_your_key header. Supports Streamable HTTP transport.

3. Start using it

Ask your AI assistant to manage your monitors (see examples below).

Available Tools

Tool Description Type
list_monitors List all monitors with status and response times Read
create_monitor Create a new HTTP monitor Write
get_monitor Get details for a specific monitor Read
update_monitor Update settings, pause/resume Write
delete_monitor Permanently delete a monitor Write
get_check_results Check history with uptime % and response times Read
get_monitor_incidents Incidents for a specific monitor Read
list_incidents All active incidents across monitors Read
list_status_pages Your public status pages Read

Examples

Example 1: Create a monitor and check its status

User prompt: "Create a monitor for https://api.example.com/health that checks every minute, then show me its details."

What happens:

  1. The AI calls create_monitor with name: "API Health", url: "https://api.example.com/health", checkInterval: 60
  2. CronAlert creates the monitor and returns its ID
  3. The AI calls get_monitor with the new ID to show the details

Expected output:

{
  "id": "abc123",
  "name": "API Health",
  "url": "https://api.example.com/health",
  "method": "GET",
  "checkInterval": 60,
  "lastStatus": "unknown",
  "createdAt": "2026-03-08T12:00:00Z"
}

Example 2: Check uptime and respond to incidents

User prompt: "Are any of my monitors down? If so, show me the error details."

What happens:

  1. The AI calls list_incidents to check for active incidents
  2. If incidents exist, it calls get_monitor for each affected monitor
  3. It calls get_check_results to get the recent error details

Expected output (no incidents):

{
  "data": [],
  "message": "No active incidents"
}

Expected output (with incident):

{
  "data": [
    {
      "id": "inc_xyz",
      "monitorId": "abc123",
      "cause": "Expected status 200, got 503",
      "startedAt": "2026-03-08T11:45:00Z"
    }
  ]
}

Example 3: List monitors and pause one for maintenance

User prompt: "List all my monitors, then pause the staging one."

What happens:

  1. The AI calls list_monitors to get all monitors
  2. It identifies the staging monitor by name
  3. It calls update_monitor with id: "staging_id" and paused: true

Expected output:

{
  "id": "staging_id",
  "name": "Staging Server",
  "isPaused": true,
  "lastStatus": "up"
}

Requirements

Privacy Policy

This MCP server connects to the CronAlert API (cronalert.com/api/v1/) using your API key. It transmits:

  • Monitor configuration (names, URLs, check intervals) when creating or updating monitors
  • API key for authentication on every request

Data is processed by CronAlert's servers on Cloudflare's infrastructure. No data is stored locally by the MCP server itself. See our full Privacy Policy for details on data collection, retention, and your rights.

Support

License

MIT

Recommended MCP Servers

How it compares

CronAlert SaaS control via MCP, not host-level metrics collection or log tailing.

FAQ

Who is CronAlert MCP for?

Developers and small teams using CronAlert who want MCP clients to manage monitors and review incidents conversationally.

When should I use CronAlert MCP?

Use it in operate and monitoring when you need to add or adjust uptime checks, inspect results, or understand incidents after you have live endpoints or scheduled jobs.

How do I add CronAlert MCP to my agent?

Install cronalert-mcp from npm, configure CronAlert API credentials per the GitHub README, add the stdio server to your MCP config, then invoke monitor and incident tools from your agent.

Monitoringmonitoringinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.