mcp-victorialogs
Provides a Model Context Protocol (MCP) server that gives tools/agents access to a VictoriaLogs instance for read-only log exploration and querying (including stream/field discovery, stats, and embedded documentation search). Supports multiple MCP transports: stdio (default), SSE, and Streamable HTTP (with /mcp endpoint) and exposes Prometheus /metrics and health checks.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
MCP server forwards authentication to VictoriaLogs via bearer token or custom headers, which supports controlled access to the upstream system. The README does not describe TLS enforcement for the MCP transport or provide details about client-side authz for the MCP endpoint itself. Secret handling best practices are not explicitly documented (assumed via standard env-var usage). Scope granularity and auditability are not described.
⚡ Reliability
Best When
You want an MCP-compatible “log knowledge + query” interface to VictoriaLogs for engineers/agents using MCP clients, preferably in an environment where you can run the server (binary/Docker) and point it at your VictoriaLogs instance.
Avoid When
You cannot supply/secure access to the underlying VictoriaLogs endpoint (e.g., need strong tenant isolation or fine-grained authorization not documented here) or you require a fully specified REST/GraphQL/SDK contract for agents beyond MCP.
Use Cases
- • Chat/agent-driven log exploration and debugging over VictoriaLogs
- • Automating log queries and metadata discovery (streams/fields/values)
- • Building observability assistant workflows that also search embedded VictoriaLogs docs offline
- • Integrating VictoriaLogs querying with MCP-capable IDEs/clients (Cursor, Claude Desktop, VS Code, etc.)
Not For
- • Write/modify VictoriaLogs data (claims are read-only APIs only)
- • Public internet exposure without considering upstream auth and network controls (configurable but not described as hardened)
- • Use cases requiring strict, well-defined API error codes/pagination semantics beyond what the MCP layer provides
Interface
Authentication
The MCP server is configured with a VictoriaLogs instance entrypoint plus optional bearer token/custom headers sent upstream. No MCP-native auth/authorization for clients is described in the README; access control is likely delegated to the MCP client environment and the upstream VictoriaLogs controls.
Pricing
No pricing details for the server are provided; it appears to be self-hostable (Go binary/Docker) and there is also a public playground instance for testing.
Agent Metadata
Known Gotchas
- ⚠ Upstream access: misconfigured VL_INSTANCE_ENTRYPOINT/headers/token will lead to failures that the MCP layer may surface as generic errors.
- ⚠ Tool breadth: many capabilities depend on the MCP client’s support for the chosen transport (stdio vs SSE vs HTTP).
- ⚠ Tool disabling: MCP_DISABLED_TOOLS may remove expected tools; agents should not assume all tools are always enabled.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-victorialogs.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.