Log inSubmit server
MCP Victorialogs logo

MCP Victorialogs

by VictoriaMetrics-Community

Connects AI clients to VictoriaLogs for log queries, instance inspection, stream discovery, statistics, and offline documentation search.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Victorialogs

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://play-vmlogs-mcp.victoriametrics.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

VictoriaMetrics-Community/mcp-victorialogs MCP server connects MCP-compatible clients to a VictoriaLogs instance through its APIs and embedded documentation. It exposes read-only capabilities for querying logs, inspecting instance parameters, listing streams and fields, retrieving field values, and examining query statistics as metrics. The server supports stdio and HTTP-based operation, with authentication and tenant settings controlled through environment variables. Reach for it when an agent needs to investigate VictoriaLogs data or consult VictoriaLogs documentation without switching tools.

Use cases

  • Query logs during incident investigation
  • Inspect available streams and fields
  • Review VictoriaLogs query statistics
  • Search VictoriaLogs documentation while debugging

Key features

  • Read-only VictoriaLogs API access
  • Log querying and exploration
  • Stream, field, and field-value discovery
  • Query statistics as metrics
  • Offline embedded documentation search
  • Stdio and Streamable HTTP modes

Tools13

What MCP Victorialogs lets your agent do. Expand a tool for its parameters.

Verified live~4.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

13/14 checks healthy over the last 77d

What it can do

From the 13 tools this server returned when we ran it.

Read-only tools · 13

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars105Stargazers on the source repository.
Last commit10d agoMost recent push to the default branch.
Tools exposed13Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Victorialogs works

What VictoriaMetrics-Community/mcp-victorialogs MCP server does

VictoriaMetrics-Community/mcp-victorialogs MCP server gives an MCP client an interface to a VictoriaLogs deployment. It is intended for log exploration, observability investigation, and debugging workflows involving either a single-node or cluster VictoriaLogs instance.

The server covers nearly all read-only APIs exposed through the VictoriaLogs web UI. It also includes a local copy of relevant VictoriaLogs documentation and can search that material without an internet connection. This lets an agent combine log results with documentation lookup in the same conversation.

How it works

The MCP process sends requests to the VictoriaLogs URL configured in VL_INSTANCE_ENTRYPOINT. Optional bearer-token and custom-header settings support instances that require authentication or specific HTTP request metadata. A default tenant can also be configured for deployments that use VictoriaLogs multi-tenancy.

The server can run over stdio, or as an HTTP service. Streamable HTTP mode is useful when the MCP endpoint must be reached over a network and also provides a root-endpoint UI with setup instructions and tool inspection. A public Streamable HTTP endpoint is available for testing with the VictoriaLogs playground, but it is intended for MCP clients rather than ordinary browser use.

Setup and configuration

VictoriaMetrics-Community/mcp-victorialogs can be installed with go install, downloaded as a release binary, run with Docker, built from source, or deployed using the documented Helm chart. Building from source requires Go 1.26 or newer. Docker examples use MCP_SERVER_MODE=http to enable Streamable HTTP mode.

Set VL_INSTANCE_ENTRYPOINT to the target VictoriaLogs URL; this is the only required environment variable. Use VL_INSTANCE_BEARER_TOKEN for API authentication, or VL_INSTANCE_HEADERS for comma-separated custom headers. In HTTP modes, MCP_PASSTHROUGH_HEADERS can forward selected incoming MCP headers to VictoriaLogs. VL_DEFAULT_TENANT_ID selects the tenant used when a request does not specify one, and MCP_SERVER_MODE selects the operating mode.

Tools and capabilities

Available functionality includes:

  • Querying and exploring VictoriaLogs records.
  • Displaying VictoriaLogs instance parameters.
  • Listing streams, fields, and values for fields.
  • Returning query statistics as metrics.
  • Searching embedded VictoriaLogs documentation offline.
  • Inspecting setup information and tools through the HTTP root endpoint.

The exact tool and prompt behavior depends on the MCP client and the model using it.

Limitations and notes

It requires access to a VictoriaLogs instance unless the public playground endpoint is used for testing. Tenant handling, authentication, and custom request headers must be configured for the target deployment when needed.

VictoriaMetrics-Community/mcp-victorialogs is designed for MCP clients. The README demonstrates Claude Desktop configuration and documents both local process and HTTP deployment patterns, but it does not document client-specific behavior beyond that example.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Victorialogs

VictoriaMetrics-Community/mcp-victorialogs is an MCP server that connects AI clients to VictoriaLogs through its APIs and embedded documentation. Its main tools support log queries, instance parameter inspection, stream and field discovery, field-value listing, query statistics, and offline VictoriaLogs documentation search.

Install it with Go, download a release binary, run the published Docker image, build it from source, or deploy the documented Helm chart. Source builds require Go 1.26 or newer, and the server must be configured with a VictoriaLogs entrypoint.

Set `VL_INSTANCE_ENTRYPOINT` to the VictoriaLogs URL and add `VL_INSTANCE_BEARER_TOKEN` or `VL_INSTANCE_HEADERS` when authentication or custom headers are required. `VL_DEFAULT_TENANT_ID` sets the tenant used when requests omit one.

Yes, the README provides a Claude Desktop configuration example. The server can be connected locally in stdio mode or remotely through its Streamable HTTP endpoint, depending on the deployment configuration.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Victorialogs AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/victoriametrics-community-mcp-victorialogs?style=directory)](https://allmcps.com/mcp/victoriametrics-community-mcp-victorialogs)
HTML Embed
<a href="https://allmcps.com/mcp/victoriametrics-community-mcp-victorialogs"><img src="https://allmcps.com/api/badge/victoriametrics-community-mcp-victorialogs?style=directory" alt="MCP Victorialogs on AllMCPs" /></a>