CronSignal

Created By
CronSignal5 months ago
Monitor cron jobs and scheduled tasks. Get alerts when they don't run, see why they failed with captured output. Create and manage monitors directly from Claude, Cursor, or any MCP-compatible AI assistant. Get started: https://cronsignal.io/
Overview

What is CronSignal?

CronSignal is a cron job monitoring service that alerts users when scheduled tasks do not run as expected. It captures the output of these tasks to help diagnose failures.

How to use CronSignal?

To use CronSignal, you need to create an API key from the CronSignal website, configure your AI assistant (like Claude or Cursor) with this key, and then set up monitors for your cron jobs.

Key features of CronSignal?

  • Real-time monitoring of cron jobs and scheduled tasks.
  • Alerts when jobs fail to run or encounter errors.
  • Captures output for debugging purposes.
  • Integration with AI assistants for easy management.

Use cases of CronSignal?

  1. Monitoring nightly backups to ensure they run successfully.
  2. Diagnosing issues with scheduled data processing tasks.
  3. Managing cron job monitors through AI assistants for streamlined operations.

FAQ from CronSignal?

  • How do I get started with CronSignal?

Visit the CronSignal website to create an API key and follow the setup instructions for your AI assistant.

  • Can I monitor multiple cron jobs?

Yes, you can set up multiple monitors for different cron jobs and manage them easily.

  • What happens if a job fails?

You will receive an alert with the captured output to help you diagnose the issue.

Server Config

{
  "mcpServers": {
    "cronsignal": {
      "command": "npx",
      "args": [
        "cronsignal-mcp"
      ],
      "env": {
        "CRONSIGNAL_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
2 months ago
Author Name
CronSignal
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

18 hours ago
Gpt Scrambler

2 days ago