MCP server "mcp-victoriametrics" as configured in VictoriaMetrics/mcp-victoriametrics. Runs in Docker (ghcr.io/victoriametrics/mcp-victoriametrics:1.20.2). Needs 7 environment variables to run.
★not rated 238▲
+1 todayA
tokens not measured
originalApache-2.0
MCP server "mcp-victorialogs" as configured in VictoriaMetrics/mcp-victorialogs. Runs in Docker (ghcr.io/victoriametrics/mcp-victorialogs:1.9.0). Needs 3 environment variables to run.
★not rated 102▲
+3 todayA
tokens not measured
originalApache-2.0
Diagnostic tools for VictoriaMetrics. Analyze query execution traces for performance bottlenecks, orchestrate multi-signal investigations across metrics, logs, traces, and alerts, and design stream aggregation rules to reduce cardinality.
★not rated 57▲
+1 5d agoA
tokens not measured
originalApache-2.0
Query the full VictoriaMetrics observability stack. Run PromQL/MetricsQL metric queries, search logs with LogsQL, discover distributed traces via Jaeger API, and manage AlertManager alerts and silences.
★not rated 57▲
+1 5d agoA
tokens not measured
originalApache-2.0
Look up VictoriaMetrics, VictoriaLogs, VictoriaTraces, operator, vmanomaly, Helm chart and Cloud documentation before naming a command-line flag, an HTTP API path or a query construct.
★not rated 57▲
+1 5d agoA
tokens not measured
originalApache-2.0
MCP server "mcp-vmanomaly" as configured in VictoriaMetrics/mcp-vmanomaly. Runs in Docker (ghcr.io/victoriametrics/mcp-vmanomaly:0.4.2). Needs 12 environment variables to run.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: