Schema | MCP Server for vmanomaly

MCP Server for vmanomaly

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_LOG_FILE`	No	Log file path (empty = stderr)	stderr
`MCP_LOG_LEVEL`	No	Log level: debug (verbose), info (default), warn, or error	info
`MCP_LISTEN_ADDR`	No	Address for HTTP server to listen on	localhost:8080
`MCP_SERVER_MODE`	No	Server operation mode. See Modes for details.	stdio
`VMANOMALY_HEADERS`	No	Custom HTTP headers for requests (comma-separated key=value pairs, e.g., X-Custom=value1,X-Auth=value2)
`MCP_DISABLED_TOOLS`	No	Comma-separated list of tools to disable
`VMANOMALY_ENDPOINT`	Yes	vmanomaly server endpoint URL (e.g., http://localhost:8490)
`MCP_DISABLE_RESOURCES`	No	Disable all resources (documentation search will continue to work)	false
`MCP_HEARTBEAT_INTERVAL`	No	Heartbeat interval for streamable-http protocol (keeps connection alive through network infrastructure)	30s
`VMANOMALY_BEARER_TOKEN`	No	Bearer token for authenticating with vmanomaly API

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VictoriaMetrics/mcp-vmanomaly'

If you have feedback or need assistance with the MCP directory API, please join our Discord server