A side-by-side look at the MCP Victoriametrics and Observability MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Victoriametrics for monitoring work over a hosted endpoint; choose Observability MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
VM_INSTANCE_ENTRYPOINT, VMC_API_KEY, VM_INSTANCE_TYPE, MCP_SERVER_MODE, MCP_LISTEN_ADDR.active_queries, alerts, documentation.list_sources, list_services, query_metrics.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 63/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | VM_INSTANCE_ENTRYPOINTVMC_API_KEYVM_INSTANCE_TYPEMCP_SERVER_MODEMCP_LISTEN_ADDR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 236 | 7 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 17 | 8 |
| Full listing | View MCP Victoriametrics | View Observability MCP |
active_queriesActive queries. This tool can determine currently active queries in the VictoriaMetrics instance.
This information is obtained from the "/api/v1/status/active_queries" HTTP endpoint of VictoriaMetrics API.alertsList of firing and pending alerts of the VictoriaMetrics instance. This tool uses `/api/v1/alerts` endpoint of vmalert API, proxied by VictoriaMetrics API.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 VictoriaMetrics related question.explain_queryExplain how MetricsQL query workslabel_valuesList of label values from VictoriaMetrics instance for a provided label name. This tool uses `/api/v1/label/{labelName}/values` endpoint of VictoriaMetrics API.labelsList of label names of the VictoriaMetrics instance. This tools uses `/api/v1/labels` endpoint of VictoriaMetrics API.metric_statisticsStatistics of metrics usage in queries of the VictoriaMetrics instance. This tool helps to identify unused (never queried) or rarely used metrics or conversely actively queried metrics. This tool uses `/api/v1/status/metric_names_stats` endpoint of VictoriaMetrics API.metricsList of available metrics of the VictoriaMetrics instance. This tool uses `/api/v1/label/__name__/values` endpoint of VictoriaMetrics API.metrics_metadataReturns stored metrics details (metadata) such as name, type, help (description), and unit, and can be used to generate natural language queries. This tool uses `/api/v1/metadata` endpoint of VictoriaMetrics API.prettify_queryPrettify (format) MetricsQL query. This tool uses `/prettify-query` endpoint of VictoriaMetrics API.queryInstant query executes PromQL or MetricsQL query expression at the given time. The result of Instant query is a list of time series matching the filter in query expression. Each returned series contains exactly one (timestamp, value) entry, where timestamp equals to the time query arg, while the value contains query result at the requested time. This tool uses `/api/v1/query` endpoint of VictoriaMetrics API.query_rangeRange query executes the query expression at the given [start…end] time range with the given step. The result of Range query is a list of time series matching the filter in query expression. Each returned series contains (timestamp, value) results for the query executed at start, start+step, start+2*step, …, start+N*step timestamps. In other words, Range query is an Instant query executed independently at start, start+step, …, start+N*step timestamps with the only difference that an instant query does not return ephemeral samples (see below). Instead, if the database does not contain any samples for the requested time and step, it simply returns an empty result. This tool uses `/api/v1/query_range` endpoint of VictoriaMetrics API.list_sourcesDiscover configured backends and connection statuslist_servicesDiscover monitored services across all backendsquery_metricsQuery metrics with pre-computed summary statsquery_logsQuery logs with error/warning counts and top patternsget_service_healthHealth score combining metrics + logs (0–100)detect_anomaliesCross-signal anomaly detection with robust (median/MAD + trend) analysisget_topologyReturn the merged infrastructure graph (resources + edges) from every topology-capable connector, filterable by source/kind/scopeget_blast_radiusPivot on the universal `RUNS_ON` relation — "if this resource's host fails, who else fails?". Works for pod→node, vm→hypervisor, container→hostPaste 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.
{
"mcpServers": {
"mcp-victoriametrics": {
"url": "https://play-mcp.victoriametrics.com/mcp"
}
}
}
{
"mcpServers": {
"observability-mcp": {
"command": "npx",
"args": [
"-y",
"@thotischner/observability-mcp"
]
}
}
}