mcp-victorialogs and mcp-victoriametrics
These are ecosystem siblings that serve different but complementary layers of the same observability stack: VictoriaMetrics handles metrics storage and querying while VictoriaLogs handles log aggregation and analysis, allowing users to instrument both signals through a unified MCP interface.
About mcp-victorialogs
VictoriaMetrics/mcp-victorialogs
The implementation of Model Context Protocol (MCP) server for VictoriaLogs.
This tool helps developers and SREs efficiently manage and debug their VictoriaLogs instances. It takes your VictoriaLogs data and system parameters as input and allows you to query logs, view instance details, list streams and fields, and get query statistics. The output includes structured log data, system information, and metrics for observability, enabling easier troubleshooting and automation.
About mcp-victoriametrics
VictoriaMetrics/mcp-victoriametrics
The implementation of Model Context Protocol (MCP) server for VictoriaMetrics
This tool helps Site Reliability Engineers and DevOps professionals more easily manage, monitor, and troubleshoot their VictoriaMetrics deployments. It acts as a bridge, allowing various client applications to access VictoriaMetrics data and APIs. You input queries or requests for metrics and configurations, and it outputs organized monitoring data, query explanations, and operational insights.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work