Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Cronitor connector, then ask in plain words. The AI picks the tools.
For developers and ops teams who watch cron jobs and scheduled tasks with Cronitor.
The AI lists your monitors with their passing or failing status and summarizes the failing ones, so you see what needs attention first.
The AI opens a monitor and reads its latest event, latest invocations and passing status, then tells you in plain words if the job is healthy.
The AI updates a monitor by key, for example to pause it with paused:true or to change the schedule. It sends only the fields you give.
Changes dataThe AI creates a monitor in Cronitor with the fields you provide, so a new job is watched from its first run.
Changes dataThe AI reports a telemetry event (run, complete, fail, ok or pause) for a monitor. This records job activity and can clear or trigger alerts.
Changes dataThe login page asks for your Cronitor API key.
Find it in Cronitor → Settings → API keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"cronitor": {
"url": "https://cronitor.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"cronitor": {
"type": "http",
"url": "https://cronitor.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cronitor API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Cronitor server only. Ask your AI to run cronitor_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with cronitor_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with cronitor_upgrade before then undoes the cancel. Or write to [email protected].
cronitor_list_monitorscronitor_get_monitorcronitor_create_monitorcronitor_update_monitorcronitor_delete_monitorcronitor_ping_monitorcronitor_usage_statuscronitor_request_featurecronitor_upgradecronitor_cancel_subscriptionFind which monitors are failing right now. Check if one job is healthy. Pause a monitor or change its schedule. Create a new monitor for a scheduled job. Send a run, complete or fail ping for a monitor. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Cronitor. The server calls the Cronitor API with your own Cronitor access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Cronitor API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cronitor API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Cronitor API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Cronitor.
Yes, if you approve it. 4 of the 6 Cronitor tools can create or change data. The other 2 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Cronitor server only. Cancel any time: your paid plan then runs to the end of the paid period. Run cronitor_usage_status to see how many calls you used.
Ask the AI to run cronitor_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run cronitor_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with cronitor_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.