The implementation of Model Context Protocol (MCP) server for VictoriaMetrics
# Add to your Claude Code skills
git clone https://github.com/VictoriaMetrics/mcp-victoriametricsGuides for using mcp servers skills like mcp-victoriametrics.
Last scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T15:53:16.595Z",
"npmAuditRan": true,
"pipAuditRan": true
}mcp-victoriametrics is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by VictoriaMetrics. The implementation of Model Context Protocol (MCP) server for VictoriaMetrics. It has 190 GitHub stars.
Yes. mcp-victoriametrics passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/VictoriaMetrics/mcp-victoriametrics" and add it to your Claude Code skills directory (see the Installation section above).
mcp-victoriametrics is primarily written in Go. It is open-source under VictoriaMetrics on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh mcp-victoriametrics against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
The implementation of Model Context Protocol (MCP) server for VictoriaMetrics.
This provides access to your VictoriaMetrics instance and seamless integration with VictoriaMetrics APIs and documentation. It can give you a comprehensive interface for monitoring, observability, and debugging tasks related to your VictoriaMetrics instances, enable advanced automation and interaction capabilities for engineers and tools.
This MCP server allows you to use almost all read-only APIs of VictoriaMetrics, i.e. all functions available in VMUI:
In addition, the MCP server contains embedded up-to-date documentation and is able to search it without online access.

More details about the exact available tools and prompts can be found in the Usage section.
You can combine functionality of tools, docs search in your prompts and invent great usage scenarios for your VictoriaMetrics instance. Just check the Dialog example section to see how it can work. And please note the fact that the quality of the MCP Server and its responses depends very much on the capabilities of your client and the quality of the model you are using.
You can also combine the MCP server with other observability or doc search related MCP Servers and get even more powerful results.
There is a publicly available instance of the VictoriaMetrics MCP Server that you can use to test the features without installing it:
https://play-mcp.victoriametrics.com/mcp
Attention! This URL is not supposed to be opened in a browser, it is intended to be used in MCP clients.
It's available in Streamable HTTP mode and configured to work with Public VictoriaMetrics Playground.
Here is example of configuration for Claude Desktop:
Just download the latest release from Releases page and put it to your PATH.
Example for Linux x86_64 (note that other architectures and platforms are also available):
latest=$(curl -s https://api.github.com/repos/VictoriaMetrics/mcp-victoriametrics/releases/latest | grep 'tag_name' | cut -d\" -f4)
wget https://github.com/VictoriaMetrics/mcp-victoriametrics/releases/download/$latest/mcp-victoriametrics_Linux_x86_64.tar.gz
tar axvf mcp-victoriametrics_Linux_x86_64.tar.gz
You can run VictoriaMetrics MCP Server using Docker.
This is the easiest way to get started without needing to install Go or build from source.
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-victoriametrics
You should replace environment variables with your own parameters.
Note that the MCP_SERVER_MODE=http flag is used to enable Streamable HTTP mode.
More details about server modes can be found in the Configuration section.
See available docker images in github registry.
Also see Using Docker instead of binary section for more details about using Docker with MCP server with clients in stdio mode.
For building binary from source code you can use the following approach:
Clone repo:
git clone https://github.com/VictoriaMetrics/mcp-victoriametrics.git
cd mcp-victoriametrics
Build binary from cloned source code:
make build
# after that you can find binary mcp-victoriametrics and copy this file to your PATH or run inplace
Build image from cloned source code:
docker build -t mcp-victoriametrics .
# after that you can use docker image mcp-victoriametrics for running or pushing
Check out VictoriaMetrics MCP Server Helm chart documentation for more details about installation using Helm.
MCP Server for VictoriaMetrics is configured via environment variables:
| Variable | Description | Required | Default | Allowed values |
|---|---|---|---|---|
VM_INSTANCE_ENTRYPOINT / VMC_API_KEY |
URL to VictoriaMetrics instance (it should be root / URL of vmsingle or vmselect) |
Yes (if you don't use VMC_API_KEY) |
- | - |
VM_INSTANCE_TYPE |
Type of VictoriaMetrics instance | Yes (if you don't use VMC_API_KEY) |
- | single, cluster |
VM_INSTANCE_BEARER_TOKEN |
Authentication token for VictoriaMetrics API | No | - | - |
VM_INSTANCE_HEADERS |
Custom HTTP headers to send with requests (comma-separated key=value pairs) | No | - | - |
MCP_PASSTHROUGH_HEADERS |
HTTP header names to forwar |