Hosting

Self-hosted local binary or Docker process; official public playground endpoint is also documented for remote clients.

Transport

stdio by default; optional SSE and Streamable HTTP.

Endpoint

https://play-mcp.victoriametrics.com/mcp

Authentication

A self-hosted instance may use an optional bearer token or custom headers; VictoriaMetrics Cloud requires a VMC_API_KEY. The documented public playground endpoint is configured against the public VictoriaMetrics playground; no user credential is listed for that demo endpoint.

Requirements

• A VictoriaMetrics single-node or cluster instance, or VictoriaMetrics Cloud account, for a private deployment.
• Install the official release binary or run the official Docker image. Building from source requires Go; the repository go.mod declares Go 1.27.1, while the README prerequisites say Go 1.26 or newer.
• Use only an instance and credentials the user is authorized to access.

Setup steps

1. For a no-install demo, add the documented remote Streamable HTTP endpoint https://play-mcp.victoriametrics.com/mcp to a client that supports remote HTTP MCP. It is intended for MCP clients and is configured for the public VictoriaMetrics playground.
2. For a private instance, install the official binary from the repository Releases page or use the official Docker image ghcr.io/victoriametrics/mcp-victoriametrics. Configure the stdio process with command `/path/to/mcp-victoriametrics` and environment variables VM_INSTANCE_ENTRYPOINT (instance root URL) and VM_INSTANCE_TYPE (`single` or `cluster`); VM_INSTANCE_BEARER_TOKEN is optional. For VictoriaMetrics Cloud use VMC_API_KEY instead.
3. Keep authentication values in the client’s secure local environment mechanism. Optional custom headers use VM_INSTANCE_HEADERS as comma-separated key=value pairs. The MCP server defaults to stdio; for HTTP mode set MCP_SERVER_MODE=http and use the documented `/mcp` path, with an appropriate private-network security posture.
4. Reconnect and inspect tools/list. In HTTP mode, the server's `/` page provides setup help and tool inspection; check `/health/readiness` for readiness. Tool availability changes with disabled-tool settings, deployment type, and credentials.
5. The public repository README and configuration reference list supported environments, transports, tools, and troubleshooting. The README and go.mod differ on the minimum Go version for source builds; using a released binary or Docker avoids that discrepancy.

The official README documents 20 common tools and 7 additional VictoriaMetrics Cloud tools. The names below are a representative subset; availability changes with deployment mode and MCP_DISABLED_TOOLS. No live tools/list count is claimed.

• query

  Execute an instant PromQL or MetricsQL query.

  01
• query_range

  Execute a range query over a time period.

  02
• metrics

  List metrics available in the configured instance.

  03
• metrics_metadata

  Read stored metric type, help, and unit metadata.

  04
• labels

  List available label names.

  05
• label_values

  List values for a selected label.

  06
• series

  List available time series.

  07
• rules

  View alerting and recording rules.

  08
• alerts

  View firing and pending alerts.

  09
• documentation

  Search embedded VictoriaMetrics documentation.

  10
• prettify_query

  Format PromQL or MetricsQL query text.

  11
• explain_query

  Parse a query and explain how it works.

  12

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• This integration connects to a user-selected metrics system and can expose potentially sensitive telemetry; use least-privilege instance credentials.
• Several tools are disabled by default, and Cloud-specific tools require VMC_API_KEY; tool availability is dynamic by configuration.
• The public playground endpoint is shared and intended for demonstration, not private production data.
• The README says source builds support Go 1.26+ while the current go.mod declares 1.27.1; binary and Docker distribution paths are documented alternatives.
• Documentation and logo were reviewed; connection, tools/list, and functionality were not tested.

• The README states Go 1.26 or newer for source builds, while the current go.mod declares Go 1.27.1. Use a released binary or Docker image unless source compilation requirements are confirmed against the selected release.

• official repository documentation

  Documents the official release binary and Docker image, public playground endpoint, required instance settings, auth options, transports, readiness endpoint, and representative available tools.

• official source runtime metadata

  Current source module declares Go 1.27.1; this conflicts with README's lower source-build minimum, so source compilation caveat is recorded.

• verified publisher organization avatar

  VictoriaMetrics organization image associated with the official repository; downloaded, decoded, and visually checked on light and dark contact sheets. Selection tier B: official developer organization avatar.

• discovery directory

  VictoriaMetrics appeared in the awesome-mcp.tools observability search results; used for discovery only.

• official or maintainer tool reference

  Maintainer repository lists a broader versioned query/alerting tool surface; current 12 rows are a partial snapshot.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.