Cronalert vs MCP Victorialogs
A side-by-side look at the Cronalert and MCP Victorialogs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cronalert for monitoring work as a local process; choose MCP Victorialogs for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cronalert when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CRONALERT_API_KEY. - You want tools like
list_monitors, create_monitor, get_monitor.
Choose MCP Victorialogs when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
VL_INSTANCE_ENTRYPOINT, VL_INSTANCE_BEARER_TOKEN, VL_INSTANCE_HEADERS, MCP_PASSTHROUGH_HEADERS, VL_DEFAULT_TENANT_ID, MCP_SERVER_MODE. - You want tools like
documentation, facets, field_names.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 57/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | CRONALERT_API_KEY | VL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 104 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | 13 |
| Full listing | View Cronalert | View MCP Victorialogs |
Tools & capabilities
Cronalert tools 12
list_monitorsList all monitors with status and response timescreate_monitorCreate an HTTP, heartbeat, or TCP port monitor (heartbeats take an expected interval and grace period)get_monitorGet details for a specific monitorupdate_monitorUpdate settings, heartbeat interval/grace, pause/resumedelete_monitorPermanently delete a monitorget_check_resultsCheck history with uptime % and response timesget_monitor_incidentsIncidents for a specific monitorlist_incidentsAll active incidents across monitorslist_status_pagesYour public status pagesadd_incident_updatePost a status update on an active incidentget_incident_updatesStatus updates for an incidentimport_monitorsImport monitors from UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, or CSV
MCP Victorialogs tools 13
documentationSearch documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaLogs related question.facetsThe most frequent values per each log field seen in the logs returned by the given <query> on the given [<start> ... <end>] time range. This tool uses `/select/logsql/facets` endpoint of VictoriaLogs API.field_namesGet field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name. This tool uses `/select/logsql/field_names` endpoint of VictoriaLogs API.field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/field_values` endpoint of VictoriaLogs API.flagsList of non-default flags (parameters) of the VictoriaLogs instance. This tools uses `/flags` endpoint of VictoriaLogs API.hitsThe number of matching log entries for the given <query> on the given [<start> ... <end>] time range grouped by <step> buckets. The returned results are sorted by time. This tool uses `/select/logsql/hits` endpoint of VictoriaLogs API.queryExecutes LogsQL query expression to search log entries. This tool uses `/select/logsql/query` endpoint of VictoriaLogs API.stats_queryLog stats for the given query at the given timestamp (time) in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query` endpoint of VictoriaLogs API.stats_query_rangeLog stats for the given query on the given [start ... end] time range with the given step interval. The stats is returned in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query_range` endpoint of VictoriaLogs API.stream_field_namesGet log stream field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name.. This tool uses `/select/logsql/stream_field_names` endpoint of VictoriaLogs API.stream_field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/stream_field_values` endpoint of VictoriaLogs API.stream_idsGet _stream_id values for the log streams from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every _stream_id. This tool uses `/select/logsql/stream_ids` endpoint of VictoriaLogs API.- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cronalert
{
"mcpServers": {
"cronalert": {
"command": "npx",
"args": [
"-y",
"cronalert-mcp"
],
"env": {
"CRONALERT_API_KEY": "YOUR_CRONALERT_API_KEY_HERE"
}
}
}
}
MCP Victorialogs
{
"mcpServers": {
"mcp-victorialogs": {
"url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
}
}
}
Frequently asked questions
Cronalert is categorized under Monitoring and uses a local stdio subprocess. MCP Victorialogs belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Cronalert for monitoring work and MCP Victorialogs for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cronalert is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. MCP Victorialogs has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cronalert and mcp-victorialogs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cronalert has a quality signal of 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Victorialogs has 63/100 (Good) with 1 views, 0 installs and 104 GitHub stars.