io.github.VictoriaMetrics/mcp-victoriametrics
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
{
"mcpServers": {
"mcp-victoriametrics": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/victoriametrics/mcp-victoriametrics:1.120.1"
],
"env": {
"VM_INSTANCE_ENTRYPOINT": "<vm_instance_entrypoint>",
"VM_INSTANCE_TYPE": "<vm_instance_type>",
"VM_INSTANCE_BEARER_TOKEN": "<your-vm_instance_bearer_token>",
"VMC_API_KEY": "<your-vmc_api_key>",
"MCP_DISABLED_TOOLS": "<mcp_disabled_tools>",
"MCP_DISABLE_RESOURCES": "<mcp_disable_resources>",
"MCP_PASSTHROUGH_HEADERS": "<mcp_passthrough_headers>"
}
}
}
}VM_INSTANCE_ENTRYPOINTURL to VictoriaMetrics instance (it should be root URL of vmsingle or vmselect), for example http://localhost:8428 or https://play.victoriametrics.com
VM_INSTANCE_TYPEType of VictoriaMetrics instance (single / cluster)
VM_INSTANCE_BEARER_TOKENAuthentication token for VictoriaMetrics API
VMC_API_KEYOptional: API key from VictoriaMetrics Cloud Console (if you have deployment in VictoriaMetrics Cloud)
MCP_DISABLED_TOOLSComma-separated list of tools to disable
MCP_DISABLE_RESOURCESDisable all resources (documentation tool will continue to work)
MCP_PASSTHROUGH_HEADERSHTTP header names to forward from incoming MCP requests to VictoriaMetrics (comma-separated list). Overrides VM_INSTANCE_HEADERS on collision.
AI-powered trading strategy development: backtesting, market data, and portfolio analysis
Feature flagging and A/B testing platform with AI-first experimentation workflows.
Query Meta Ads performance data — accounts, campaigns, ad sets, ads, metrics & settings.