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

Q: How do I install the Cronitor (Cron Monitoring) MCP Server in Claude Desktop?

Open your claudedesktopconfig.json file and add the server configuration under the mcpServers key. Restart the Claude Desktop app completely to let the stdio transport initialize. You will see a hammer icon appear in the chat box when the tools are active.

Q: What is the quickest way to check my RUM site health with this server?

Tell your agent to run the listsites tool to see all registered properties. From there, query getsiteerrors to see if your frontend is throwing uncaught exceptions.

Control your Cronitor cron jobs, heartbeats, and status pages directly from Claude Desktop.

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 Desktop

Create your Vinkius account to connect Cronitor (Cron Monitoring) to Claude Desktop 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 Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fast status page and monitor configuration

The `create_monitor` and `create_status_page` tools let your AI client build out your monitoring infrastructure directly from chat. You don't need to open the browser dashboard to configure a new heartbeat or set up a public status page. When you need to replicate setups, this MCP Server clones configurations instantly. If a service goes down for scheduled work, tell Claude to run `create_maintenance_window` to avoid false alerts.

Immediate incident response in Claude Desktop

The `list_issues` and `update_issue` tools keep you informed of active alerts without switching windows. Your agent pulls the exact failure details, so you see what broke and when. If a cluster of cron jobs fails at once, the `bulk_issues` tool resolves or acknowledges them in one shot. Run `pause_monitor` to stop alerts while you deploy a hotfix.

Real-time analytics and telemetry queries

The `get_metrics` and `query_site_analytics` tools pull raw performance data straight into your chat interface. You get exact numbers on request duration, failure rates, and visitor locations without running custom SQL or API scripts. If you notice a sudden spike in errors, the `get_site_errors` tool isolates the problematic endpoints immediately. Your agent reads this data to pinpoint the exact failure pattern.

Setup guide

Set up Cronitor (Cron Monitoring) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Cronitor (Cron Monitoring) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Cronitor (Cron Monitoring) MCP configuration

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

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under cronitor-cron-monitoring-mcp.

json

{
  "mcpServers": {
    "cronitor-cron-monitoring-mcp": {
      "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 Desktop

Open your `claude_desktop_config.json` file and add the server configuration under the `mcpServers` key. Restart the Claude Desktop app completely to let the stdio transport initialize. You will see a hammer icon appear in the chat box when the tools are active.

Yes, you add this remote server as a custom connector in your browser settings. Go to Settings, click Integrations, and paste the hosted HTTPS URL provided by Vinkius to access all 44 Cronitor tools without any local installation of the MCP Server.

Ask your agent to pause the specific monitor or the entire group. It executes the `pause_monitor` or `pause_group` tool with the appropriate parameters. Once your deployment finishes, tell the agent to resume them by setting the pause value to zero.

Tell your agent to run the `list_sites` tool to see all registered properties. From there, query `get_site_errors` to see if your frontend is throwing uncaught exceptions.

Your API keys and telemetry metrics are processed inside an isolated, ephemeral V8 sandbox. Vinkius secures these credentials and never logs the raw payload values. Only the specific tool calls you authorize are passed to the external monitoring endpoints.

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