Mcp Victorialogs
Let your coding agent query VictoriaLogs and read docs through MCP while you debug production log pipelines.
Overview
mcp-victorialogs is a MCP server for the Operate phase that integrates VictoriaLogs API access and documentation into agent-driven log monitoring workflows.
What is this MCP server?
- OCI image ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0 with stdio transport
- Connects agents to VictoriaLogs API plus bundled documentation context
- Requires VL_INSTANCE_ENTRYPOINT (root URL for vmsingle or vlselect) and VL_INSTANCE_BEARER_TOKEN
- Optional MCP_DISABLED_TOOLS to trim tool surface for least-privilege setups
- Community-maintained alongside VictoriaMetrics ecosystem—not a generic log grep skill
- [object Object]
Community signal: 84 GitHub stars.
What problem does it solve?
When logs live in VictoriaLogs, manually jumping between dashboards, API calls, and docs slows incident response and confuses agent-assisted debugging.
Who is it for?
Indie operators already on VictoriaLogs who want MCP-native log queries and doc grounding from Claude Code or Cursor.
Skip if: Teams without a VictoriaLogs or vlselect/vmsingle endpoint, or builders who only need local dev logs without a remote log stack.
What do I get? / Deliverables
After configuration with your instance URL and token, your agent can use MCP tools backed by VictoriaLogs API and docs to investigate and explain log data in context.
- Authenticated MCP bridge to your VictoriaLogs instance
- Agent-invokable log and documentation tools
- Configurable tool allowlist via MCP_DISABLED_TOOLS
Recommended MCP Servers
Journey fit
Log investigation and observability are ongoing production concerns, so Operate is the natural journey phase. Monitoring is the precise facet because the server integrates VictoriaLogs API and documentation for log analytics workflows.
How it compares
VictoriaLogs-specific monitoring MCP integration, not a universal cloud observability marketplace.
Common Questions / FAQ
Who is mcp-victorialogs for?
It is for developers and solo operators who run VictoriaLogs and want their MCP-enabled coding agent to query logs and use VictoriaLogs documentation.
When should I use mcp-victorialogs?
Use it during operate and incident workflows when you need agent help investigating VictoriaLogs data or understanding LogSQL and deployment docs.
How do I add mcp-victorialogs to my agent?
Run the published OCI image with stdio, set VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN, optionally MCP_DISABLED_TOOLS, and register the server in your MCP host config.