How to Use the Cronitor (Cron Monitoring) MCP in Claude Code

Q: How do I add the Cronitor (Cron Monitoring) MCP Server to Claude Code?

Run claude mcp add --transport http cronitor -- in your terminal. Once added, Claude Code registers the MCP Server for instant command-line access.

Q: Can I manage alerts with Cronitor (Cron Monitoring) in Claude Code?

Yes. You can pause alerts using pausemonitor or update notification groups with updatenotification directly from your command prompt.

Q: How does Claude Code query metrics from Cronitor (Cron Monitoring)?

Claude Code invokes getmetrics with your specified parameters. It formats the performance data directly inside your terminal window for fast analysis.

Q: Can I create RUM sites with this CLI tool?

Yes, Claude Code uses createsite to set up real user monitoring. You can also delete them using deletesite when tearing down test environments.

Control your Cronitor monitors, metrics, and alerts directly from your terminal with Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cronitor (Cron Monitoring) MCP to Claude Code

Create your Vinkius account to connect Cronitor (Cron Monitoring) to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cronitor (Cron Monitoring) with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Headless cron diagnostics for terminal power users

This Cronitor MCP Server lets you debug production issues right from your shell by calling `list_issues` through Claude Code. You pipe the output of failing monitors into grep or other command-line utilities. No browser tabs needed. You query `get_metrics` directly from the terminal to see execution times and failure rates for any job.

Automated shell script monitoring via Claude Code

Claude Code uses `create_monitor` to quickly register new shell scripts and cron jobs you write in the terminal. It hooks them up to the telemetry endpoint by calling `send_telemetry` in your test runs. You can script the entire setup process. The agent writes the bash script, adds the ping commands, and registers the monitor in one terminal session.

Rapid environment and group management

When spinning up fresh staging environments, Claude Code runs `create_environment` to isolate your test monitors. It groups them using `create_group` to keep your dashboard clean. If you need to mute alerts for a deploy, the agent uses `pause_group` to pause everything instantly. You keep your focus on the terminal while your environments configure themselves.

Setup guide

Set up Cronitor (Cron Monitoring) MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see cronitor-cron-monitoring-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Cronitor (Cron Monitoring) transactions." It will automatically discover and invoke the available Cronitor (Cron Monitoring) tools.

Terminal

claude mcp add --transport http cronitor-cron-monitoring-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Cronitor (Cron Monitoring) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "cronitor-cron-monitoring-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cronitor. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cronitor (Cron Monitoring) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cronitor (Cron Monitoring) MCP in Claude Code

Run `claude mcp add --transport http cronitor -- ` in your terminal. Once added, Claude Code registers the MCP Server for instant command-line access.

Yes. You can pause alerts using `pause_monitor` or update notification groups with `update_notification` directly from your command prompt.

Claude Code invokes `get_metrics` with your specified parameters. It formats the performance data directly inside your terminal window for fast analysis.

Yes, Claude Code uses `create_site` to set up real user monitoring. You can also delete them using `delete_site` when tearing down test environments.

Telemetry events and API keys are processed in the secure Vinkius V8 Isolate Sandbox. Your credentials are never stored on your disk or exposed in plaintext in your terminal history.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript