Can AI agents automate VictoriaMetrics?

VictoriaMetrics is automatable today through its HTTP APIs. This record is the VictoriaMetrics time-series database, including single-node, cluster, and VictoriaMetrics Cloud as named in the MCP README. VictoriaLogs, VictoriaTraces, and Anomaly Detection were not reviewed. The URL examples document Prometheus-compatible HTTP endpoints, including /api/v1/query and /api/v1/query_range on single-node and cluster select paths, and an insert path for Prometheus text at /insert/.../prometheus/api/v1/import/prometheus. The MCP README says a bearer token can authenticate the VictoriaMetrics API, and that VictoriaMetrics Cloud can use an API key from the Cloud console instead of an instance URL. The VictoriaMetrics organization publishes mcp-victoriametrics. The README says the server exposes read-only VictoriaMetrics APIs for queries, labels, rules, cardinality, and documentation search. It supports stdio, SSE, and streamable HTTP. A public playground is documented at https://play-mcp.victoriametrics.com/mcp against the public VictoriaMetrics playground. Linux x86_64 is the binary example on that README. The public GitHub API for VictoriaMetrics/VictoriaMetrics reports the Apache License 2.0. Connector catalogs were not opened. Computer-use viability is unassessed. API scores 7. MCP scores 7. API is the best path because the HTTP API includes the import path, while the MCP server is documented as read-only.

Best path today: api · Overall automatability: 7/10