Mcp-vmanomaly MCP Server

Mcp-vmanomaly is an MCP integration. MCP Server for vmanomaly - VictoriaMetrics anomaly detection.

Packages and local setup

The published oci package is ghcr.io/victoriametrics/mcp-vmanomaly:0.4.2. Its declared MCP transport is stdio.

The package declares VMANOMALY_ENDPOINT (required): vmanomaly server endpoint URL (e.g., http://localhost:8490); VMANOMALY_BEARER_TOKEN: Bearer token for authenticating with vmanomaly API; VMANOMALY_BEARER_TOKEN_FILE: Path to a file containing a bearer token; mutually exclusive with VMANOMALY_BEARER_TOKEN; VMANOMALY_HEADERS: Custom HTTP headers for vmanomaly requests (comma-separated key=value pairs, e.g., X-Custom-Header=value1,X-Another=value2); MCP_SERVER_MODE: MCP server mode: stdio (default), sse, or http; MCP_LISTEN_ADDR: Listen address for SSE/HTTP modes (default: localhost:8080); MCP_LOG_LEVEL: Log level: debug, info (default), warn, or error; MCP_LOG_FILE: Log file path (empty = stderr); MCP_ENABLED_TOOLS: Comma-separated positive allowlist of tools; empty enables all registered tools; MCP_DISABLED_TOOLS: Comma-separated denylist of tools; takes precedence over MCP_ENABLED_TOOLS; MCP_HEARTBEAT_INTERVAL: Heartbeat interval for HTTP mode (default: 30s); MCP_DISABLE_RESOURCES: Disable embedded documentation resources; documentation search remains available.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.4.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.