The VictoriaTraces MCP Server provides access to a VictoriaTraces instance, enabling integration with its APIs for trace querying and analysis. It offers a comprehensive interface for observability and debugging tasks.
From the registry: MCP Server for VictoriaTraces. Provides integration with VictoriaTraces API and documentation
$ go install github.com/VictoriaMetrics-Community/mcp-victoriatraces/cmd/mcp-victoriatraces@latesthttps://github.com/VictoriaMetrics-Community/mcp-victoriatraces/releasesPlease install the `mcp-victoriatraces` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install mcp-victoriatraces binary** — Go install or download from Releases Run: `go install github.com/VictoriaMetrics-Community/mcp-victoriatraces/cmd/mcp-victoriatraces@latest` (https://github.com/VictoriaMetrics-Community/mcp-victoriatraces/releases)
- **VictoriaTraces instance** — A running VictoriaTraces single-node or cluster (https://docs.victoriametrics.com/victoriatraces/)
Canonical MCP server config (stdio transport):
- command: `mcp-victoriatraces`
- args: []
- required environment variables:
- `VT_INSTANCE_ENTRYPOINT`: URL to VictoriaTraces instance (example: `https://localhost:10428`)
- optional environment variables:
- `VT_INSTANCE_BEARER_TOKEN`: Bearer token (example: `<your-bearer-token>`)
- `VT_INSTANCE_HEADERS`: Custom HTTP headers (comma-separated) (example: `X-Scope-OrgID=1`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.VT_INSTANCE_ENTRYPOINTrequiredURL to VictoriaTraces instanceReal-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.