@crontinel/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRONTINEL_API_KEY | Yes | Your Crontinel API key | |
| CRONTINEL_API_URL | No | Override the API base URL (self-hosted or local dev) | https://app.crontinel.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_scheduled_jobsA | List all monitored cron commands with their last run status and timing |
| get_cron_statusA | Get the last run status, exit code, and duration for a specific cron command |
| get_queue_statusA | Get queue depth, failed job count, and oldest job age for all queues or a specific queue |
| get_horizon_statusA | Get a snapshot of Laravel Horizon health: supervisor states, paused status, failed jobs per minute |
| list_recent_alertsA | List alerts that have fired in the last N hours |
| acknowledge_alertA | Dismiss an active alert by its alert key |
| create_alertB | Create a new alert channel (slack, email, or webhook) for the app |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: listing vs. getting cron status, queue vs. Horizon status, and alert listing/acknowledgment/creation. Descriptions clearly differentiate overlapping monitoring concepts.
All tool names follow a consistent verb_noun pattern: list_, get_, acknowledge_, create_. No mixed conventions, making the set predictable and easy to navigate.
Seven tools is well-scoped for a monitoring server, covering the core areas (cron, queues, Horizon, alerts) without unnecessary redundancy.
The set covers monitoring and alert management comprehensively, but lacks an update/delete for alert channels and a detail view for individual alerts. Minor gaps that agents can work around.