VictoriaMetrics MCP Server
Usage stats for the VictoriaMetrics MCP server appear once 5+ Willow orgs use this connector.
Fast, cost-effective monitoring solution and time-series database compatible with Prometheus
What is the VictoriaMetrics MCP Server?
The VictoriaMetrics MCP server gives AI agents structured, permission-aware access to VictoriaMetrics through the Model Context Protocol. With 24 pre-built actions, agents can read, create, and update VictoriaMetrics data on behalf of authorized users.
Willow ships the VictoriaMetrics MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how VictoriaMetrics is being used by every AI agent in your stack.
Tools
Execute Instant Query
Execute a MetricsQL query at a single point in time. MetricsQL is a PromQL-compatible query language with additional functions and optimizations. Returns the current value of metrics matching the query. Use this for getting the latest state of metrics, checking current values, or evaluating expressions at a specific timestamp.
Execute Range Query
Execute a MetricsQL query over a range of time. Returns time series data over the specified time window with the given resolution step. Use this for plotting graphs, analyzing trends over time, or getting historical metric values. VictoriaMetrics optimizes range queries for better performance than Prometheus. Supports relative time ranges and automatic step adjustment.
Query Top K Series
Find the top K time series by value using VictoriaMetrics' optimized topk functions. Returns only the highest-value series, which is more efficient than fetching all series and sorting. Use this for identifying top consumers, finding anomalies, or focusing on the most important metrics. Supports both instant and range queries with topk operators.
Execute Query with Trace
Execute a MetricsQL query and get detailed execution trace information. Returns query results along with performance metrics and execution steps. Use this for debugging slow queries, understanding query execution, optimizing performance, or troubleshooting unexpected results. VictoriaMetrics provides enhanced tracing compared to Prometheus.
Find Series by Label Matchers
Find time series that match specific label selectors. Returns a list of label sets identifying each matching series. Use this to discover what metrics exist, find series with specific labels, or explore available time series data. VictoriaMetrics supports extended label matching with =, !=, =~, !~ operators and can handle high-cardinality series efficiently.
List All Label Names
Get a list of all label names used across time series. Returns an array of label name strings. Use this to discover what labels are available, understand the labeling scheme, or build dynamic queries. VictoriaMetrics can efficiently handle databases with millions of unique labels. Supports filtering by time range and series matchers.
Get Label Values
Get all values for a specific label name. Returns an array of strings representing all unique values that label has across time series. Use this to discover what instances, jobs, or other label values exist in your metrics. VictoriaMetrics can efficiently return values even for high-cardinality labels. Supports time range filtering.
Get Metric Metadata
Get metadata about metrics including type and help text. Returns information about what each metric measures and its type (counter, gauge, histogram, summary). Use this to understand available metrics and their purposes. Note: VictoriaMetrics may have limited metadata compared to Prometheus if metrics are imported without metadata.
Get TSDB Statistics
Get cardinality statistics about the time series database. Returns information about the number of series, label names, label value pairs, and which labels have the highest cardinality. Use this to understand TSDB resource usage, identify high-cardinality labels causing performance or storage issues, plan capacity, or troubleshoot. VictoriaMetrics provides additional statistics compared to Prometheus.
List Metric Names
Get a list of all metric names (time series names) available in VictoriaMetrics. Returns an array of __name__ label values, which are the metric names. Use this for discovering what metrics are being stored, building metric browsers, or validating metric ingestion. Can be filtered by time range and label matchers. This is a convenience wrapper around finding series and extracting __name__ labels.
Import JSON Data
Import time series data in JSON line format. Each line should be a JSON object with metric, values, and timestamps arrays. Use this for bulk data import, migrating from other systems, or restoring exported data. VictoriaMetrics efficiently handles large imports. The format is VictoriaMetrics native JSON export format.
Import Prometheus Data
Import time series data in Prometheus text exposition format. Accepts the same format that Prometheus scrape targets expose. Use this for importing data from Prometheus exporters, migrating from Prometheus, or ingesting data in the standard Prometheus format. Each line contains metric name, labels, value, and optional timestamp.
Import CSV Data
Import time series data in CSV format. Flexible format supporting various CSV layouts. Use this for importing data from spreadsheets, databases, or other CSV sources. You specify the CSV format including which columns contain metric names, labels, values, and timestamps. VictoriaMetrics supports custom delimiters and various timestamp formats.
Import Native Format
Import time series data in VictoriaMetrics native binary format. This is the most efficient import format with best performance and lowest overhead. Use this for bulk migrations from other VictoriaMetrics instances, large backups, or when maximum import speed is needed. The data must be in VictoriaMetrics native export format (obtained via /api/v1/export/native).
Write Prometheus Remote Write
Write time series data using Prometheus Remote Write protocol. This is the standard protocol for writing metrics to VictoriaMetrics from Prometheus, vmagent, or other compatible clients. Use this for streaming metrics ingestion, setting up remote write from Prometheus, or programmatic data insertion. Accepts Prometheus protobuf format.
Export Series as JSON
Export time series data in JSON line format. Each line is a JSON object with metric labels, values array, and timestamps array. Use this for backing up data, migrating to another system, or analyzing data externally. Supports filtering by time range and series matchers. Can export large datasets efficiently. The exported data can be re-imported using Import JSON Data.
Export Series as CSV
Export time series data in CSV format with customizable structure. You specify which labels and fields to include in the CSV columns. Use this for importing into spreadsheets, databases, or data analysis tools. Supports various timestamp formats and flexible column layout. Good for creating reports or analyzing data with external tools.
Export Series in Native Format
Export time series data in VictoriaMetrics native binary format. This is the most efficient export format with best performance, smallest size, and lowest overhead. Use this for bulk backups, migrating to another VictoriaMetrics instance, or when you need maximum export speed. The exported data can be re-imported using Import Native Format for fast restoration.
Export Specific Time Range
Export time series data for a specific time range with automatic format selection. Efficiently exports data between two timestamps, automatically choosing the best format based on data size. Use this for creating point-in-time backups, extracting specific time periods, or archiving historical data. Supports all major export formats.
Delete Time Series
Delete time series matching label selectors. Permanently removes data from VictoriaMetrics storage. Use this to comply with data retention policies, remove test data, clean up unwanted metrics, or handle data deletion requests. Can delete specific time ranges or entire series. CAUTION: This operation is permanent and cannot be undone. Consider taking a backup first.
Reset Rollup Result Cache
Clear the rollup result cache in VictoriaMetrics. The rollup cache stores computed query results to speed up repeated queries. Use this after data corrections, when troubleshooting query results, or when you need to ensure fresh calculations. VictoriaMetrics will rebuild the cache as needed. This doesn't delete data, only cached query results.
Get Build Info
Get VictoriaMetrics server build information including version, build date, and Go version. Use this to verify which version you're running, check for available updates, troubleshoot compatibility issues, or report bugs. Returns version string and build metadata. Essential for understanding available features and bug fixes.
Health Check
Check if VictoriaMetrics server is healthy and responding to requests. Returns 200 OK if the server is running and processing requests. Use this for load balancer health checks, monitoring system availability, or automated health monitoring. This is a lightweight endpoint that doesn't perform heavy operations.
Get Active Queries
Get a list of currently executing queries on the VictoriaMetrics server. Shows query text, execution time, client information, and resource usage. Use this to monitor query performance, identify long-running or expensive queries, troubleshoot performance issues, or detect query abuse. Essential for operational monitoring and query optimization.
Customize Tools
Edit descriptions, modify arguments, select tools, or add new ones
Set Up Your VictoriaMetrics MCP Server in Minutes
Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.
Claude Desktop
{
"mcpServers": {
"willow-victoria-metrics": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/victoria-metrics"
}
}
}Cursor
{
"mcpServers": {
"willow-victoria-metrics": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/victoria-metrics"
}
}
}Claude Code
claude mcp add willow-victoria-metrics --transport http https://<org>.mcp-s.com/mcp/mcp/victoria-metricsn8n
{
"url": "https://<org>.mcp-s.com/mcp/mcp/victoria-metrics",
"method": "POST"
}Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.
Enterprise Governance for VictoriaMetrics
Willow adds the layer VictoriaMetrics and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.
VictoriaMetrics MCP Server FAQ
What is the VictoriaMetrics MCP server?
The VictoriaMetrics MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write VictoriaMetrics data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.
How is Willow's VictoriaMetrics MCP server different from the official one?
The official VictoriaMetrics MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.
Which AI clients work with the VictoriaMetrics MCP server?
Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.
Is the VictoriaMetrics MCP server secure? How does Willow handle authentication?
Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in VictoriaMetrics, nothing more. No credentials reach the LLM. Every action writes to an audit trail.
Can I limit which VictoriaMetrics actions agents can take?
Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.
How do I detect shadow VictoriaMetrics MCP servers in my org?
Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved VictoriaMetrics MCP locally, you'll see it.
What does the VictoriaMetrics MCP server cost?
Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.
How do I install the VictoriaMetrics MCP server with Willow?
Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.
Compare Willow MCP Gateway
See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.
Your agents are already in the wild.
Give them a Basecamp. Go from AI chaos to AI work, in minutes.