The VictoriaLogs MCP Server provides access to a VictoriaLogs instance, enabling read-only API functionalities for querying logs, exploring data, and retrieving instance parameters.
From the registry: MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation

$ go install github.com/VictoriaMetrics/mcp-victorialogs/cmd/mcp-victorialogs@latesthttps://github.com/VictoriaMetrics/mcp-victorialogs/releasesPlease install the `mcp-victorialogs` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install mcp-victorialogs binary** — Go install or download from Releases Run: `go install github.com/VictoriaMetrics/mcp-victorialogs/cmd/mcp-victorialogs@latest` (https://github.com/VictoriaMetrics/mcp-victorialogs/releases)
- **VictoriaLogs instance** — A running VictoriaLogs single-node or cluster instance (https://docs.victoriametrics.com/victorialogs/)
Canonical MCP server config (stdio transport):
- command: `mcp-victorialogs`
- args: []
- required environment variables:
- `VL_INSTANCE_ENTRYPOINT`: URL to VictoriaLogs instance (example: `https://victorialogs.example.com`)
- optional environment variables:
- `VL_INSTANCE_BEARER_TOKEN`: Bearer token for VictoriaLogs API (example: `<your-bearer-token>`)
- `VL_INSTANCE_HEADERS`: Custom HTTP headers (comma-separated key=value) (example: `X-Scope-OrgID=1`)
Note: Public playground at https://play-vmlogs-mcp.victoriametrics.com/mcp. sse and http server modes also available.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.VL_INSTANCE_ENTRYPOINTrequiredURL to VictoriaLogs instanceReal-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.