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