# yincongcyincong/VictoriaMetrics-mcp-server [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/yincongcyincong/VictoriaMetrics-mcp-server  
**GitHub Stars:** 8  
**npm Downloads (last month):** 162  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/yincongcyincong-victoriametrics-mcp-server

## Description
An MCP server for interacting with VictoriaMetrics database.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "victoriametrics-mcp-server": {
    "command": "npx",
    "args": ["-y","@smithery/cli"],
    "env": {
      "VM_URL": "",
      "VM_SELECT_URL": "",
      "VM_INSERT_URL": ""
    }
  }
}
```

**Requires environment variables:** `VM_URL`, `VM_SELECT_URL`, `VM_INSERT_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What yincongcyincong/VictoriaMetrics-mcp-server MCP server does

The yincongcyincong/VictoriaMetrics-mcp-server MCP server connects an MCP client with VictoriaMetrics operations. It supports writing metric samples, importing metrics in Prometheus exposition format, evaluating PromQL expressions, querying data across a time range, and inspecting label names and values.

The available operations cover both ingestion and read access. A client can provide a metric object with values and Unix-second timestamps, submit a string containing Prometheus exposition data, or issue PromQL queries. Label discovery is available without query parameters for the complete label-name list, while label-value lookup requires a label name.

## How it works

The server is launched as a local Node-based MCP process. The documented NPX configuration starts the published package with the `-y` flag and passes VictoriaMetrics connection settings through the process environment. The debug example runs the project entry point with Node and sets `VM_URL` to a local VictoriaMetrics address.

Query tools accept PromQL. `vm_query` evaluates the current value of a time series and can optionally receive an evaluation timestamp. `vm_query_range` accepts a PromQL expression and optionally takes Unix-second start and end times plus a resolution step such as `10s` or `1m`.

## Setup and configuration

The yincongcyincong/VictoriaMetrics-mcp-server MCP server is shown in the README as an NPX package named `@yincongcyincong/victoriametrics-mcp-server`. Its Claude Desktop configuration defines these environment variables:

- `VM_URL`
- `VM_SELECT_URL`
- `VM_INSERT_URL`

The README does not provide default endpoint values for the three configuration entries. The debug command demonstrates `VM_URL=http://127.0.0.1:8428` for a local VictoriaMetrics instance. Smithery installation is also documented for Claude Desktop, but the direct NPX configuration identifies the server package and its runtime settings more explicitly.

## Tools and capabilities

The documented tools are:

- `vm_data_write`: writes a metric object, an array of numeric values, and matching Unix-second timestamps.
- `vm_prometheus_write`: imports a string in Prometheus exposition format.
- `vm_query_range`: evaluates PromQL over an optional start time, end time, and step width.
- `vm_query`: evaluates PromQL at the current time or an optional Unix-second timestamp.
- `vm_labels`: returns unique label names and takes no input.
- `vm_label_values`: returns unique values for a required label name.

## Limitations and notes

The README documents the tool inputs and endpoint environment variables but does not describe authentication, TLS options, retry behavior, response schemas, or version compatibility. `vm_query_range` requires only `query`; its time range and step fields are optional. The write tools require their documented data fields, including values and timestamps for `vm_data_write`.

The yincongcyincong/VictoriaMetrics-mcp-server MCP server is therefore best evaluated against the VictoriaMetrics endpoint layout in the target deployment before use. In particular, the README lists separate general, select, and insert endpoint variables without explaining when each one is used.

_Full upstream README: https://allmcps.com/mcp/yincongcyincong-victoriametrics-mcp-server/readme_