# Cronly — how to use (mcp.ai)

Connect your Cronly account and use 10 tools for server monitoring straight from your AI agent. Connect with your own API key. Cronly monitors cron jobs, SSL certificates, servers, and crontab backups and reports operational alerts.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_cronly?ms=1787293380000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `cronly_create_certificate`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/cronly`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/cronly/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/cronly/create/certificate` — Create an SSL/TLS certificate-expiry monitor for a hostname and port.
  - body: { port?: integer, hostname: string, project_id?: integer }
- `POST https://api.mcp.ai/api/cronly/create/monitor` — Create a cron-job heartbeat monitor and return its ID and sensitive pulse token.
  - body: { name: string, duration: integer, schedule: string, timezone: string, project_id?: integer }
- `POST https://api.mcp.ai/api/cronly/create/project` — Create a project for organizing Cronly monitors and certificate checks.
  - body: { name: string }
- `POST https://api.mcp.ai/api/cronly/delete/certificate` — Permanently delete an SSL/TLS certificate monitor by numeric ID.
  - body: { certificate_id: integer }
- `POST https://api.mcp.ai/api/cronly/delete/monitor` — Permanently delete a cron-job monitor by numeric ID.
  - body: { monitor_id: integer }
- `POST https://api.mcp.ai/api/cronly/delete/project` — Permanently delete a Cronly project by numeric ID.
  - body: { project_id: integer }
- `POST https://api.mcp.ai/api/cronly/get/company` — Return safe organization, timezone, and subscription-summary fields for the connected Cronly account without exposing billing or integration secrets.
- `POST https://api.mcp.ai/api/cronly/get/resource` — Get one monitor, project, certificate, user, server, or backup by its resource identity.
  - body: { username?: string, resource_id: integer|string, resource_type: string }
- `POST https://api.mcp.ai/api/cronly/list/resources` — List notifications, monitors, projects, certificates, users, servers, or backups. Notifications return one page with a continuation cursor; other resource types return their complete arrays.
  - body: { per_page?: integer, next_cursor?: string, resource_type: string }
- `POST https://api.mcp.ai/api/cronly/pulse/monitor` — Record a successful heartbeat for a monitor using its sensitive pulse token. This changes monitor run state even though Cronly exposes it as GET.
  - body: { pulse_token: string }

## Example prompts
- "What can I do in Cronly?"
- "Show me a summary of my Cronly account"

## More
- Page: https://mcp.ai/cronly
- Agent spec (llms.txt): https://mcp.ai/cronly/llms.txt
- Postman collection: https://mcp.ai/cronly/postman.json