Practical overview
When it fits
Use it when an MCP-compatible client needs read-oriented access to a VictoriaMetrics instance for observability investigation, query analysis or documentation lookup.
Who it is for
- Engineers using an MCP-compatible assistant to investigate VictoriaMetrics data.
- Teams adding VictoriaMetrics context to an MCP-based monitoring or operations workflow.
Documented uses
- Query and explore metrics, labels, label values and time series.
- Inspect instance parameters, cardinality and metrics usage.
- Analyze alerts and recording rules, and investigate queries.
- Debug relabeling, downsampling and retention configurations.
- Search VictoriaMetrics documentation from an MCP client.
Requirements & limits
A public MCP endpoint is available for use through MCP clients and is configured for the VictoriaMetrics Playground. For a self-hosted connection, the documented requirements include a VictoriaMetrics or VictoriaMetrics Cloud instance. Go 1.26 or higher is required only when building from source. The project is licensed under Apache-2.0.
- The tool connects to VictoriaMetrics or VictoriaMetrics Cloud; it is not a standalone assistant.
- The exposed APIs are described as almost all read-only, so the documented focus is investigation rather than changing data or settings.
- Graph display depends on the MCP client's capabilities.
- Response quality depends on the MCP client and model.
- Installation options include release binaries, Docker and source builds.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Run the VictoriaMetrics MCP server with Docker
Start the MCP server in SSE mode connected to a VictoriaMetrics instance.
Before you start
- Docker
- A VictoriaMetrics or VictoriaMetrics Cloud instance; the example uses the public VictoriaMetrics Playground.
Steps
Run the documented Docker command, replacing its environment values with your instance settings: `docker run -d --name mcp-victoriametrics -e VM_INSTANCE_ENTRYPOINT=https://play.victoriametrics.com -e VM_INSTANCE_TYPE=cluster -e MCP_SERVER_MODE=sse -e MCP_LISTEN_ADDR=:8080 -p 8080:8080 ghcr.io/victoriametrics/mcp-victo
For Streamable HTTP mode, use
MCP_SERVER_MODE=httpinstead ofsse.Configure an MCP client to connect to the server using the mode selected; consult the repository's Configuration and Usage sections for client and mode details.
Expected outcome
The container is configured to run the VictoriaMetrics MCP server on port 8080 and connect it to the configured VictoriaMetrics instance.
Guide limitations
- The example values target the public Playground and must be changed for another instance.
- The server exposes almost all VictoriaMetrics read-only APIs; the README describes these as read-only capabilities.
- MCP server response quality depends on the capabilities of the client and the model used.
Build the MCP server binary from source
Build the VictoriaMetrics MCP server binary from a cloned repository.
Before you start
- Go 1.26 or higher.
- A VictoriaMetrics or VictoriaMetrics Cloud instance is listed as a server requirement.
Steps
Clone the repository: the command below.
git clone https://github.com/VictoriaMetrics/mcp-victoriametrics.gitChange into the repository directory:
cd mcp-victoriametrics.Build the binary with the command below.
make buildUse the generated
mcp-victoriametricsbinary in place or copy it to your PATH.
Expected outcome
The repository build produces a `mcp-victoriametrics` binary.
Guide limitations
- This recipe covers building the binary, not configuring or starting the server.
- Go 1.26 or higher is required to build from source.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- VictoriaMetrics/mcp-victoriametrics · Official homepage title · retained in its source language

