- SILENCED
- LOGGED
- TRACKED
- HUMAN
Short answer
How do I schedule maintenance windows with my AI?
You tell your agent when a deployment or downtime is starting, and it uses Cronitor to silence incoming alerts. This keeps your notification channels clean while you work. You'll see how the agent handles the window and the resulting issue states below.
Maintenance outcomes
Where your downtime management lands.
The agent moves data between Cronitor and your alert groups based on your commands.
SILENCED
Quiet alert groups
The agent uses the pause tool to stop notifications for specific groups. You won't get pinged for expected downtime.
LOGGED
Active maintenance logs
The agent creates a window in Cronitor to mark the period. This provides a record of why things were quiet.
TRACKED
Managed incident states
The agent handles the lifecycle of issues. It updates existing issues to reflect that they are part of a planned event.
HUMAN
Manual oversight needed
The agent cannot delete your Cronitor accounts or change your core notification settings. You stay in control of the infrastructure.
The workflow
What your AI does when the downtime starts.
Instead of you logging into a dashboard, your agent executes the necessary API calls to keep your monitoring quiet.
Silence the noise
The agent stops specific alert groups from firing so you don't get flooded with false positives during a deploy.
pause_groupMark the window
The agent tells Cronitor exactly when the maintenance starts and ends to keep your history accurate.
create_maintenance_windowHandle active issues
If an issue is already open, the agent can modify its state to show it's part of the current maintenance.
update_issueLog new incidents
If something unexpected happens during the window, the agent can record it as a new entry.
create_issue
Try it
Copy these to start.
Use these prompts to trigger the Cronitor tools.
Starting points
Swap the bracketed text for your actual group names or issue IDs.
Cronitor Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Cronitor capabilities are ready to use.
{
"mcpServers": {
"cronitor-cron-monitoring-mcp": {
"url": "https://edge.vinkius.com/vk_preview_EHNlqUmdOzFgXZGMmL53K1EbEQVA8FefmcOzppi4/mcp"
}
}
}Pause the 'Production API' alert group for the next two hours.
Create a maintenance window for the 'Database Cluster' starting now.
Update issue #452 to show it's part of the current deployment.
Create a new issue in Cronitor for the 'Frontend' group regarding the latency spike.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Cronitor once, then ask.
Just link your account once. Your credentials stay encrypted, and you can immediately start managing Cronitor through your agent.
Connect Cronitor to your AIFAQ
How this task behaves.
- 01
Can the AI delete my alert groups?
No. The agent can only pause groups or create new windows and issues.
- 02
Will the AI automatically resume alerts after the window ends?
The agent follows your specific instructions. If you tell it to pause a group, it stays paused until you tell it to unpause.
- 03
Can the AI change my Cronitor billing settings?
No. The agent only has access to the tools provided in the manifest.
- 04
Does the agent see all my Cronitor data?
The agent can see the data required to perform the actions you request, like group names and issue IDs.
- 05
Can the AI fix the underlying server issue?
No. The agent only manages the monitoring state in Cronitor. You still have to fix the actual code or infrastructure.
More questions about Cronitor? See everything the Cronitor Connector can do
Connect Cronitor to Claude, Cursor, ChatGPT & more
