Skip to main content
Glama
VictoriaMetrics-mcp-server

VictoriaMetrics-mcp-server

VictoriaMetrics MCP Server

Trust Score

MCP Server for the VictoriaMetrics.

Installing via Smithery

To install VictoriaMetrics Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @yincongcyincong/victoriametrics-mcp-server --client claude

Debug

npx @modelcontextprotocol/inspector -e VM_URL=http://127.0.0.1:8428  node src/index.js

NPX

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

📊 VictoriaMetrics Tools API Documentation

Related MCP server: ClickHouse MCP Server

1. vm_data_write

Description: Write data to the VictoriaMetrics database.

Input Parameters:

Parameter

Type

Description

Required

metric

object

Tags of the metric

✅

values

number[]

Array of metric values

✅

timestamps

number[]

Array of timestamps in Unix seconds

✅


2. vm_prometheus_write

Description: Import Prometheus exposition format data into VictoriaMetrics.

Input Parameters:

Parameter

Type

Description

Required

data

string

Metrics in Prometheus exposition format

✅


3. vm_query_range

Description: Query time series data over a specific time range.

Input Parameters:

Parameter

Type

Description

Required

query

string

PromQL expression

✅

start

number

Start timestamp in Unix seconds

⛔️

end

number

End timestamp in Unix seconds

⛔️

step

string

Query resolution step width (e.g., 10s, 1m)

⛔️

Only query is required; the other fields are optional.


4. vm_query

Description: Query the current value of a time series.

Input Parameters:

Parameter

Type

Description

Required

query

string

PromQL expression to evaluate

✅

time

number

Evaluation timestamp in Unix seconds

⛔️


5. vm_labels

Description: Get all unique label names.

Input Parameters: None


6. vm_label_values

Description: Get all unique values for a specific label.

Input Parameters:

Parameter

Type

Description

Required

label

string

Label name to get values for

✅


Available Tools

6 tools
vm_data_writeC

Write data to the VM database

Inputs: metric (required), values (required), timestamps (required).

vm_labelsB

Get all unique label names

Inputs: no named parameters.

vm_label_valuesC

Get all unique values for a specific label

Inputs: label (required).

vm_prometheus_writeC

mport Prometheus exposition format data into VictoriaMetrics

Inputs: data (required).

vm_queryC

Query current value of a time series

Inputs: query (required), time.

vm_query_rangeC

Query time series over a time range

Inputs: query (required), start, end, step.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: writing data, retrieving metadata about labels, querying current values, and querying over time ranges. The descriptions make it easy to differentiate between tools like vm_query (current value) and vm_query_range (time range).

    Naming Consistency5/5

    All tools follow a consistent 'vm_' prefix with snake_case naming, using descriptive verb_noun patterns (e.g., vm_data_write, vm_query_range). There are no deviations in style or convention across the set.

    Tool Count5/5

    With 6 tools, this is well-scoped for a VictoriaMetrics server, covering core operations like data ingestion, label exploration, and querying without being overwhelming. Each tool earns its place in the workflow.

    Completeness4/5

    The toolset covers essential CRUD-like operations for time series data: writing (vm_data_write, vm_prometheus_write), reading (vm_query, vm_query_range), and metadata exploration (vm_labels, vm_label_values). A minor gap might be the lack of explicit deletion or update tools, but agents can work around this given the domain's typical usage patterns.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers