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.

mcp-victorialogs
48
Emerging
mcp-victoriametrics
46
Emerging
Maintenance 13/25
Adoption 8/25
Maturity 9/25
Community 18/25
Maintenance 13/25
Adoption 10/25
Maturity 9/25
Community 14/25
Stars: 55
Forks: 14
Downloads: —
Commits (30d): 0
Language: Go
License: Apache-2.0
Stars: 130
Forks: 16
Downloads: —
Commits (30d): 0
Language: Go
License: Apache-2.0
No Package No Dependents
No Package No Dependents

About mcp-victorialogs

VictoriaMetrics/mcp-victorialogs

The implementation of Model Context Protocol (MCP) server for VictoriaLogs.

Exposes VictoriaLogs' read-only APIs—including log querying, stream/field enumeration, and query statistics—through MCP tools alongside embedded, searchable documentation for offline access. Supports multiple deployment modes (stdio, HTTP) with environment-based configuration for authentication and multi-tenancy, enabling AI clients like Claude Desktop to perform log analysis and debugging tasks directly against VictoriaLogs instances.

About mcp-victoriametrics

VictoriaMetrics/mcp-victoriametrics

The implementation of Model Context Protocol (MCP) server for VictoriaMetrics

Exposes VictoriaMetrics' read-only APIs through MCP tools, enabling querying, metric exploration, rule analysis, and cardinality debugging directly from AI clients. Operates in multiple modes (stdio, HTTP/SSE) with embedded documentation searchable offline, allowing seamless integration with Claude and other MCP-compatible clients without external API calls.

Scores updated daily from GitHub, PyPI, and npm data. How scores work