VictoriaTraces MCP Server implements the Model Context Protocol (MCP) to expose your VictoriaTraces instance through MCP-compatible interactions. It provides access to VictoriaTraces data and seamless integration with VictoriaTraces APIs and documentation, delivering a comprehensive interface for traces, observability, and debugging tasks related to your VictoriaTraces deployments. The server exposes read-only APIs such as retrieving services and operations (span names) and querying traces to explore and analyze trace data. It also ships with embedded, up-to-date VictoriaTraces documentation and a built-in search capability so you can access information even offline. The project includes a toolbox of built-in tools (documentation, services, service_names, traces, trace, dependencies) and pre-defined prompts to assist common tasks. It supports multiple transports (stdio, SSE, HTTP) and exposes endpoints for streaming, messaging, metrics, and health checks. The MCP server can be used standalone or combined with other MCP servers to extend observability workflows. Configuration is via environment variables (VT_INSTANCE_ENTRYPOINT, VT_INSTANCE_BEARER_TOKEN, VT_INSTANCE_HEADERS) and is subject to client and model capabilities.