Skip to content
Zed

mcp vmanomaly for Zed

io.github.victoriametrics/mcp-vmanomaly

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

client:Zed transport:stdio runtime:oci

Install mcp vmanomaly in Zed

~/.config/zed/settings.json · windows: %APPDATA%\Zed\settings.json

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "context_servers": {
    "mcp-vmanomaly": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/victoriametrics/mcp-vmanomaly:0.4.2"
      ],
      "env": {
        "VMANOMALY_ENDPOINT": "<VMANOMALY_ENDPOINT>",
        "VMANOMALY_BEARER_TOKEN": "<VMANOMALY_BEARER_TOKEN>",
        "VMANOMALY_BEARER_TOKEN_FILE": "<VMANOMALY_BEARER_TOKEN_FILE>",
        "VMANOMALY_HEADERS": "<VMANOMALY_HEADERS>",
        "MCP_SERVER_MODE": "<MCP_SERVER_MODE>",
        "MCP_LISTEN_ADDR": "<MCP_LISTEN_ADDR>",
        "MCP_LOG_LEVEL": "<MCP_LOG_LEVEL>",
        "MCP_LOG_FILE": "<MCP_LOG_FILE>",
        "MCP_ENABLED_TOOLS": "<MCP_ENABLED_TOOLS>",
        "MCP_DISABLED_TOOLS": "<MCP_DISABLED_TOOLS>",
        "MCP_HEARTBEAT_INTERVAL": "<MCP_HEARTBEAT_INTERVAL>",
        "MCP_DISABLE_RESOURCES": "<MCP_DISABLE_RESOURCES>"
      }
    }
  }
}

Merge this into your existing settings object — do not replace the file. Zed docs

mcp vmanomaly in other clients