LabStore
← All labs

VictoriaTraces

by docker ✓ verified ✓ Packaged by Docker

Provides access to your VictoriaTraces instance and seamless integration with VictoriaTraces APIs and documentation. It can give you a comprehensive interface for tracing, observability, and debugging tasks related to your VictoriaTraces instances, enable advanced automation and interaction capabilities for engineers and tools.

MCP server installable needs setup network: on runtime: sysbox

Monitoring & Uptime MCP Servers

VictoriaTraces MCP Server

Provides access to your VictoriaTraces instance and seamless integration with VictoriaTraces APIs and documentation. It can give you a comprehensive interface for tracing, observability, and debugging tasks related to your VictoriaTraces instances, enable advanced automation and interaction capabilities for engineers and tools.

What is an MCP Server?

MCP Info

Attribute Details
Docker Image ghcr.io/victoriametrics-community/mcp-victoriatraces
Author VictoriaMetrics-Community
Repository https://github.com/VictoriaMetrics-Community/mcp-victoriatraces

Image Building Info

Attribute Details
Dockerfile https://github.com/VictoriaMetrics-Community/mcp-victoriatraces/blob/19e84f1819a03e4ea6af971d04e7f0f669a98d9e/Dockerfile
Commit 19e84f1819a03e4ea6af971d04e7f0f669a98d9e
Docker Image built by VictoriaMetrics-Community
Docker Scout Health Score Not available
Verify Signature Not available
Licence Apache License 2.0

Available Tools (6)

Tools provided by this Server Short Description
dependencies Service dependency graph
documentation Search documentation resources
service_operations List of span names (operations) of a service
services List of all services
trace Trace information
traces Query traces

Tools Details

Tool: dependencies

Query the service dependency graph. This tools uses /select/jaeger/api/dependencies endpoint of VictoriaTraces API.

Parameters Type Description
endTs number optional The end timestamp in unix milliseconds. Current timestamp will be used if empty.
lookback number optional the lookbehind window duration in milliseconds (i.e. start-time + lookback = endTs). Default to 1h if empty.
tenant string optional Name of the tenant for which the data will be displayed (format AccountID:ProjectID)

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: documentation

Search documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaTraces related question.

Parameters Type Description
query string Query for search (for example, list of keywords)
limit number optional Maximum number of results to return

This tool is read-only. It does not modify its environment.

Tool: service_operations

Get all the span names (operations) of a service. This tool uses /select/jaeger/api/services/{service_name}/operations endpoint of VictoriaTraces API.

Parameters Type Description
service_name string Service name
tenant string optional Name of the tenant for which the data will be displayed (format AccountID:ProjectID)

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: services

List of all traced services. This tools uses /select/jaeger/api/services endpoint of VictoriaTraces API.

Parameters Type Description
tenant string optional Name of the tenant for which the data will be displayed (format AccountID:ProjectID)

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: trace

Get trace info by trace ID. This tool uses /select/jaeger/api/traces/{trace_id} endpoint of VictoriaTraces API.

Parameters Type Description
trace_id string Trace ID
tenant string optional Name of the tenant for which the data will be displayed (format AccountID:ProjectID)

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: traces

Query traces. This tool uses /select/jaeger/api/traces endpoint of VictoriaTraces API.

Parameters Type Description
limit number The maximum number of traces in query results, default 20.
service string Service name
end number optional End timestamp in unix milliseconds.
maxDuration string optional The maximum duration of the span, with units: ns, us, ms, s, m, or h.
minDuration string optional The minimum duration of the span, with units: ns, us, ms, s, m, or h.
operation string optional The span name (also known as the operation name in Jaeger)
start number optional Start timestamp in unix milliseconds.
tenant string optional Name of the tenant for which the data will be displayed (format AccountID:ProjectID)

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Use this MCP Server

{
  "mcpServers": {
    "victoriatraces": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VT_INSTANCE_ENTRYPOINT",
        "-e",
        "VT_INSTANCE_HEADERS",
        "-e",
        "MCP_SERVER_MODE",
        "-e",
        "MCP_LISTEN_ADDR",
        "-e",
        "MCP_DISABLED_TOOLS",
        "-e",
        "MCP_HEARTBEAT_INTERVAL",
        "-e",
        "VT_INSTANCE_BEARER_TOKEN",
        "ghcr.io/victoriametrics-community/mcp-victoriatraces"
      ],
      "env": {
        "VT_INSTANCE_ENTRYPOINT": "https://play-vtraces.sandbox.victoriametrics.com",
        "VT_INSTANCE_HEADERS": "HEADER2=HEADER_VALUE,HEADER2=HEADER_VALUE_2",
        "MCP_SERVER_MODE": "stdio",
        "MCP_LISTEN_ADDR": ":8081",
        "MCP_DISABLED_TOOLS": "hits,facets",
        "MCP_HEARTBEAT_INTERVAL": "30s",
        "VT_INSTANCE_BEARER_TOKEN": "<instance_bearer_token_for_authentication>"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?