vm_data_write
Write data to the VM database
LABSCO SUMMARY
Reads and writes are configured as separate URLs, which is how a cluster deployment is actually split.
Three addresses instead of one means a cluster with distinct select and insert endpoints works without a proxy standing in front of it. Label discovery is what makes a query writable in the first place: the label list and then its values turn a guess about a metric's dimensions into something you can filter on. Both ingestion paths are present — structured values with their timestamps, and raw Prometheus exposition text taken unchanged.
What it is
A VictoriaMetrics client covering ranged and instant reads, label discovery, and two write paths.
What you get
- A range query with start, end and step, and an instant query at a single point in time.
- Every unique label name, and every value of one label.
- Metrics written directly with their timestamps and values.
- Prometheus exposition format imported as it stands.
Requirements
A reachable VictoriaMetrics deployment with VM_URL, VM_SELECT_URL and VM_INSERT_URL all configured — reads and writes are addressed separately.
Setup effort
One command — npx -y @yincongcyincong/victoriametrics-mcp-server
USE CASES
01
Plotting how a metric moved across a window
Start, end and step decide the resolution, which is what separates a usable series from a wall of points.
02
Working out which labels a metric actually carries
A query cannot be filtered until its dimensions are known, and guessing label names is how empty results happen.
03
Getting data in from something that already speaks Prometheus
Exposition text goes in unchanged, which avoids a conversion step; structured writes cover everything that does not.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
vm_label_values
Get all unique values for a specific label
vm_labels
Get all unique label names
vm_prometheus_write
mport Prometheus exposition format data into VictoriaMetrics
vm_query
Query current value of a time series
vm_query_range
Query time series over a time range
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected.
Requires
- npx on PATH
- A reachable VictoriaMetrics deployment, its addresses filled in as VM_URL, VM_SELECT_URL and VM_INSERT_URL in the block's env
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"victoriametrics": {
"command": "npx",
"args": [
"-y",
"@yincongcyincong/victoriametrics-mcp-server"
],
"env": {
"VM_URL": "",
"VM_SELECT_URL": "",
"VM_INSERT_URL": ""
}
}
}
}VM_URL, VM_SELECT_URL and VM_INSERT_URL are the addresses of your VictoriaMetrics deployment; the project's own debug command sets VM_URL=http://127.0.0.1:8428
npx
TERMINAL
npx -y @yincongcyincong/victoriametrics-mcp-server
