SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Cronly to Claude

Connect Claude Web, Desktop and Cowork to Cronly MCP. List failed cron jobs today, check ssl certificates expiring soon, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Cronly logoCronly
Api Key

Cronly is an operations monitoring service for cron jobs, SSL certificates, servers, and crontab backups. It helps teams catch failures and expiry risks early with clear operational alerts.

10 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Cronly account to Claude via Composio Connect, enabling it to list failed cron jobs today, check SSL certificates expiring soon, summarize active Cronly server alerts, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Cronly with

ChatGPTHermesAtomic Agent

Connecting Cronly to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Cronly account

Back in Claude, ask it to connect to Cronly or give it any Cronly-related task.

For example, ask Claude to:

  • "List failed cron jobs today"
  • "Check SSL certificates expiring soon"
  • "Summarize active Cronly server alerts"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Cronly account is ready to use.

What is the Cronly Claude Connector, and what's possible with it?

The Cronly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Cronly account. It provides structured and secure access so your agent can perform Cronly operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Cronly?

The connector can show as connected, but Claude must use it in each Cronly conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Cronly again.

2. Why does Claude show an MCP server error before Cronly connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Cronly.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Cronly.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Cronly authorization link not work?

The Composio connector is one server. Your Cronly account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Cronly connection.
  • Composio creates a fresh Cronly authorization link.
  • Open that link in your browser and finish the Cronly sign-in.

4. Why do Cronly actions fail after they worked before?

The Cronly connection can expire or lose permission.

  • Ask Claude to inspect the Cronly connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Cronly account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Cronly.
  • If the action still fails with a permission error, check that the connected account has that permission in Cronly itself.

5. How do I switch to a different Cronly account?

Claude can manage the Cronly connection for you.

  • Ask Claude to disconnect or delete the current Cronly account.
  • Ask Claude to connect Cronly again.
  • Open the new Composio authorization link for Cronly.
  • Sign in with the other Cronly account in the browser.
  • After the account connects, ask Claude to retry the Cronly task.

6. Why is my Cronly connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Cronly connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Cronly tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Cronly.
TOOLS

Supported Tools

Every Cronly action and event your agent gets out of the box.

Create Certificate Monitor

Create an SSL/TLS certificate-expiry monitor for a hostname and port.

Create Monitor

Create a cron-job heartbeat monitor and return its ID and sensitive pulse token.

Create Project

Create a project for organizing Cronly monitors and certificate checks.

Delete Certificate Monitor

Permanently delete an SSL/TLS certificate monitor by numeric ID.

Delete Monitor

Permanently delete a cron-job monitor by numeric ID.

Delete Project

Permanently delete a Cronly project by numeric ID.

Get Company

Return safe organization, timezone, and subscription-summary fields for the connected Cronly account without exposing billing or integration secrets.

Get Resource

Get one monitor, project, certificate, user, server, or backup by its resource identity.

List Resources

List notifications, monitors, projects, certificates, users, servers, or backups.

Pulse Monitor

Record a successful heartbeat for a monitor using its sensitive pulse token.

FRAMEWORKS

How to build Cronly MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Cronly MCP with ChatGPT

Hermes logo

Hermes

Use Cronly MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Cronly MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone Cronly MCP server, the agents and LLMs can only access a fixed set of Cronly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Cronly and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Cronly tools.

Yes, absolutely. You can configure which Cronly scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Cronly data and credentials are handled as safely as possible.

Start with Cronly.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Cronly tool your agent needs.Free to start.

Start building