M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
V

VictoriaMetrics MCP Server

Official
Official VictoriaMetrics MCP server for seamless integration with VictoriaMetrics API and documentation.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #16 of 438
Stars
★ 237 Very popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Prebuilt binary · Docker · Go 1.26+ · Hosted (no local runtime)
Credentials
Optional API key
License
Apache-2.0
Last commit
Tools
30
69FMRS · C

VictoriaMetrics MCP Server is an official, high-quality server with a rich toolset and documentation search, well-suited for monitoring scenarios. Setup is straightforward, but attention should be paid to resource consumption and API permission management.

Strongest · Maintenance 16/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
15/20
Maintenance
16/20
Documentation
15/20
Setup experience
13/20
Why each score
Reliability 10/20
Source code shows clear initialization and tool listing, but no verifiable tests or CI demonstrating key paths, so actual startup and tool behavior consistency is uncertain. Error handling and dependency control are documented but static review cannot confirm.
Security and permissions 15/20
Credentials are managed via environment variables, marked as secret, and no real tokens appear in examples. Tools are primarily read-only with no destructive default operations. However, least-privilege, data-flow disclosure, and confirmation mechanisms are not fully evident in source, so deduction applied.
Maintenance 16/20
Repository is active with ongoing commits and releases, license is Apache-2.0. However, issue response speed and dependency update policy not evaluated, and security response channel not explicitly stated.
Documentation 15/20
README provides thorough installation, configuration, client setup, and troubleshooting info, with clear tool and prompt lists. But lacks detailed tool parameters, limitations, and cost docs; some assumptions remain implicit.
Setup experience 13/20
Installation steps are clear with binary, Docker, Helm, and source options, and mainstream client config examples are provided. But static review lacks execution verification, and Docker/client examples are somewhat complex, so not full marks.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Developers and SREs using VictoriaMetrics for monitoring and observability.
  • Engineers who want to leverage AI assistants to simplify metric queries and operations.
  • Teams needing quick access to documentation and troubleshooting guides.

Not for

  • Users who do not use VictoriaMetrics; this server is not suitable for other monitoring systems.
  • Scenarios requiring write or modify operations, as the server only supports read-only APIs.
  • Environments sensitive to resource consumption, as the embedded documentation vector database may increase memory and CPU usage.

Required permissions

  • Read access to VictoriaMetrics instance APIs (query, list metrics, export data, etc.).
  • If using Cloud mode, access to VictoriaMetrics Cloud API key.
  • Network access to connect to the VictoriaMetrics instance or Cloud service may be required.

Risks and side effects

  • Need to carefully manage API tokens to avoid leaking sensitive data.
  • AI-generated queries and configurations may contain errors; should be verified before use in production.
  • The server may consume significant resources, especially when loading the documentation vector database; can save resources by disabling the documentation tool.

Setup

Before you start

Runtime：Prebuilt binary · Docker · Go 1.26+ · Hosted (no local runtime)

VM_INSTANCE_ENTRYPOINT required Root URL of the VictoriaMetrics instance (vmsingle or vmselect), e.g. http://localhost:8428.
VM_INSTANCE_TYPE required Instance type: single or cluster.
VM_INSTANCE_BEARER_TOKEN optionalsecret Bearer token for the VictoriaMetrics API, from your instance's auth configuration.
VMC_API_KEY optionalsecret API key generated in the VictoriaMetrics Cloud Console, for connecting to cloud deployments.
Other optional settings (10)
VM_INSTANCE_HEADERS optional Custom HTTP headers sent with requests, as comma-separated key=value pairs.
MCP_PASSTHROUGH_HEADERS optional HTTP header names forwarded from incoming MCP requests to VictoriaMetrics; only applies in sse/http modes.
VM_DEFAULT_TENANT_ID optional Default tenant ID in cluster mode, format accountID or accountID:projectID.
MCP_SERVER_MODE optional Server mode: stdio (default), sse, or http.
MCP_LISTEN_ADDR optional Listen address for sse/http modes, default localhost:8080.
MCP_DISABLED_TOOLS optional Comma-separated list of tools to disable, e.g. export,flags.
MCP_DISABLE_RESOURCES optional Set true to disable all resources (documentation tool keeps working).
MCP_HEARTBEAT_INTERVAL optional Heartbeat interval for streamable-http mode, default 30s.
MCP_LOG_FORMAT optional Log output format: text or .
MCP_LOG_LEVEL optional Minimum log level: debug, info, warn, error.
  1. Download the binary from GitHub Releases, or use Docker: docker run -d --name mcp-victoriametrics -e VM_INSTANCE_ENTRYPOINT=... -e VM_INSTANCE_TYPE=... -p 8080:8080 ghcr.io/victoriametrics/mcp-victoriametrics.
  2. Set environment variables: VM_INSTANCE_ENTRYPOINT (required, root URL of VictoriaMetrics instance) and VM_INSTANCE_TYPE (required, single or cluster). Optional: VM_INSTANCE_BEARER_TOKEN, VM_INSTANCE_HEADERS, VMC_API_KEY for Cloud.
  3. Configure the server in your MCP client, specifying the command path and environment variables. For example, for Claude Desktop, edit claude_desktop_config.json.

Check that it works

After starting the server, tools such as query, metrics, and tenants should appear in your MCP client's tool list; ask "What tenants are available in my VM?" — a returned tenant list confirms the connection works.

Troubleshooting

  1. Ensure `VM_INSTANCE_ENTRYPOINT` is a reachable root URL (e.g., http://localhost:8428) and the instance type is correct (single or cluster).
  2. Check that environment variables are set correctly, especially authentication tokens.
  3. If using Cloud mode, ensure `VMC_API_KEY` is valid and has required permissions.
  4. Check server logs (set `MCP_LOG_LEVEL` to debug) for error details.
  5. In SSE/HTTP modes, use `/health/liveness` and `/health/readiness` endpoints to check server status.

Things to try

Once connected, you can ask your AI assistant things like:

  • What tenants are available in my VictoriaMetrics instance?
  • List the available metrics and show which ones have never been queried (use metric_statistics)
  • Explain and prettify this query: rate(node_cpu_seconds_total[5m])
  • Search the documentation for how downsampling works in VictoriaMetrics

Tools 30

query read-only
Execute instant PromQL/MetricsQL queries
query_range read-only
Execute range PromQL/MetricsQL queries over a time period
metrics read-only
List available metrics
metrics_metadata read-only
Get stored metrics metadata (type, help, unit)
labels read-only
List available label names
label_values read-only
List values for a specific label
series read-only
List available time series
export read-only
Export raw time series data to JSON or CSV (disabled by default)
Show 22 more tools
rules read-only
View alerting and recording rules
alerts read-only
View current alerts (firing and pending)
flags read-only
View non-default flags of the VictoriaMetrics instance (disabled by default)
metric_statistics read-only
Get metrics usage (in queries) statistics
active_queries read-only
View currently executing queries
top_queries read-only
View most frequent or slowest queries
tsdb_status read-only
View TSDB cardinality statistics
tenants read-only
List available tenants in multi-tenant cluster setup
documentation read-only
Search in embedded VictoriaMetrics documentation
metric_relabel_debug read-only
Debug Prometheus-compatible relabeling rules (disabled by default)
downsampling_filters_debug read-only
Debug downsampling configuration (disabled by default)
retention_filters_debug read-only
Debug retention filters configuration (disabled by default)
prettify_query read-only
Prettify and format PromQL/MetricsQL queries
explain_query read-only
Parse PromQL/MetricsQL queries and explain how it works
test_rules read-only
Unit-test alerting and recording rules using vmalert tool (disabled by default)
deployments read-only
List available deployments in VictoriaMetrics Cloud
cloud_providers read-only
List available cloud providers in VictoriaMetrics Cloud
regions read-only
List available cloud providers regions in VictoriaMetrics Cloud
tiers read-only
List available deployment tiers in VictoriaMetrics Cloud
access_tokens read-only
List available deployment access tokens in VictoriaMetrics Cloud
rule_filenames read-only
List available alerting and recording rule filenames in VictoriaMetrics Cloud
rule_file read-only
Content of a specific alerting or recording rule file in VictoriaMetrics Cloud

Use cases

Query metrics and explore data via natural language, without writing PromQL manually.
Analyze alerting and recording rules, debug relabel configurations.
Monitor VictoriaMetrics instance health, including cardinality, query statistics, and active queries.
Search official documentation and blogs for quick troubleshooting information.
Integrate with VictoriaMetrics Cloud to manage deployments and access tokens.

Supported clients

Claude Desktop
Cursor
Claude CodePartial support
CodexPartial support
VS Code
Zed
JetBrains IDEsPartial support
Windsurf

Listed from the project's documentation, not tested by this site.

Overview

VictoriaMetrics MCP Server is the official implementation of the Model Context Protocol (MCP) server for VictoriaMetrics. It provides AI assistants with the ability to interact with VictoriaMetrics instances, enabling natural language querying of metrics, data exploration, alert rule analysis, relabel configuration debugging, and more. It includes an embedded vector database of VictoriaMetrics documentation for offline search. The server supports multiple transport modes (stdio, SSE, Streamable HTTP) and is configurable via environment variables.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 1a9d356ee337 Data synced 2026-10-12 Read the FMRS scoring method