Back to MCP Servers

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

To add mcp-vmanomaly to Claude, run the install command below. Restart Claude Code after adding it and its tools show up in your next conversation. It needs 10 environment variables, listed below.

DevTools

Install

docker run -i --rm ghcr.io/victoriametrics-community/mcp-vmanomaly:0.1.0

Environment variables

VMANOMALY_ENDPOINTSet in your MCP config
VMANOMALY_BEARER_TOKENSet in your MCP config
VMANOMALY_HEADERSSet in your MCP config
MCP_SERVER_MODESet in your MCP config
MCP_LISTEN_ADDRSet in your MCP config
MCP_LOG_LEVELSet in your MCP config
MCP_LOG_FILESet in your MCP config
MCP_DISABLED_TOOLSSet in your MCP config
MCP_HEARTBEAT_INTERVALSet in your MCP config
MCP_DISABLE_RESOURCESSet in your MCP config

What this does

mcp-vmanomaly exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

VMANOMALY_ENDPOINT
VMANOMALY_BEARER_TOKEN
VMANOMALY_HEADERS
MCP_SERVER_MODE
MCP_LISTEN_ADDR
MCP_LOG_LEVEL
MCP_LOG_FILE
MCP_DISABLED_TOOLS
MCP_HEARTBEAT_INTERVAL
MCP_DISABLE_RESOURCES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install mcp-vmanomaly?

The install section on this page carries the maker's install command for mcp-vmanomaly, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with mcp-vmanomaly?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to mcp-vmanomaly as well.

Does mcp-vmanomaly need an API key?

Yes. Before it can run, set these environment variables: VMANOMALY_ENDPOINT, VMANOMALY_BEARER_TOKEN, VMANOMALY_HEADERS, MCP_SERVER_MODE, MCP_LISTEN_ADDR, MCP_LOG_LEVEL, MCP_LOG_FILE, MCP_DISABLED_TOOLS, MCP_HEARTBEAT_INTERVAL, MCP_DISABLE_RESOURCES. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-victoriametrics-community-mcp-vmanomaly)](https://clauderules.net/mcp/io-github-victoriametrics-community-mcp-vmanomaly)
HTML
<a href="https://clauderules.net/mcp/io-github-victoriametrics-community-mcp-vmanomaly" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-victoriametrics-community-mcp-vmanomaly" alt="Listed on clauderules.net" /></a>