VictoriaMetrics/mcp-victoriatraces

The implementation of Model Context Protocol (MCP) server for VictoriaTraces.
This provides access to your VictoriaTraces instance and seamless integration with VictoriaTraces APIs and documentation.
It can give you a comprehensive interface for traces, observability, and debugging tasks related to your VictoriaTraces instances, enable advanced automation and interaction capabilities for engineers and tools.
Features
This MCP server allows you to use almost all read-only APIs of VictoriaTraces:
- Get services and operations (span names)
- Query traces, explore and analyze traces data
In addition, the MCP server contains embedded up-to-date documentation and is able to search it without online access.
More details about the exact available tools and prompts can be found in the Usage section.
You can combine functionality of tools, docs search in your prompts and invent great usage scenarios for your VictoriaTraces instance.
And please note the fact that the quality of the MCP Server and its responses depends very much on the capabilities of your client and the quality of the model you are using.
You can also combine the MCP server with other observability or doc search MCP Servers and get even more powerful results.
Requirements
- VictoriaTraces instance: (single-node or cluster)
- Go 1.25 or higher (if you want to build from source)
Installation
Go
Binaries
Just download the latest release from Releases page and put it to your PATH.
Example for Linux x86_64 (note that other architectures and platforms are also available):
Docker
You can run VictoriaTraces MCP Server using Docker.
This is the easiest way to get started without needing to install Go or build from source.
You should replace environment variables with your own parameters.
Note that the MCP_SERVER_MODE=http flag is used to enable Streamable HTTP mode.
More details about server modes can be found in the Configuration section.
See available docker images in github registry.
Also see Using Docker instead of binary section for more details about using Docker with MCP server with clients in stdio mode.
Source Code
For building binary from source code you can use the following approach:
- Clone repo:
- Build binary from cloned source code:
- Build image from cloned source code:
Helm
Check out VictoriaTraces MCP Server Helm chart documentation for more details about installation using Helm.
Configuration
MCP Server for VictoriaTraces is configured via environment variables:
| Variable | Description | Required | Default | Allowed values |
|----------------------------|---------------------------------------------------------|----|--------|------------------------|
| VT_INSTANCE_ENTRYPOINT | URL to VictoriaTraces instance | Yes | - | - |
| VT_INSTANCE_BEARER_TOKEN | Authentication token for VictoriaTraces API | No | - | - |
| VT_INSTANCE_HEADERS | Custom HTTP headers to send with requests (comma-separated key=value pairs) | No | - | - |
| VT_DEFAULT_TENANT_ID | Default tenant ID used when tenant is not specified in requests (format: AccountID:ProjectID or AccountID) | No | 0:0 | - |
| MCP_SERVER_MODE | Server operation mode. See Modes for details. | No | stdio | stdio, sse, http |
| MCP_LISTEN_ADDR | Address for SSE or HTTP server to listen on | No | localhost:8081 | - |
| MCP_DISABLED_TOOLS | Comma-separated list of tools to disable | No | - | - |
| MCP_HEARTBEAT_INTERVAL | Defines the heartbeat interval for the streamable-http protocol. It means the MCP server will send a heartbeat to the client through the GET connection, to keep the connection alive from being closed by the network infrastructure (e.g. gateways) | No | 30s | - |