MCP Server

MCP Server for VictoriaTraces. Provides integration with VictoriaTraces API and documentation. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 12 defined tools rather than through you.

What it actually does

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

Its toolset

Everything the assistant can do here goes through one of these:

• documentation — Search in embedded VictoriaTraces documentation
• services — List of all traced services
• service_names — Get all the span names (operations) of a service
• traces — Query traces
• trace — Get trace info by trace ID
• dependencies — Query the service dependency graph
• Binaries — Just download the latest release from Releases page and put it to your
• Modes — MCP Server supports the following modes of operation (transports):
• Cursor — Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server and paste the following configuration into your Cursor ~/.cursor/mcp.json file:
• Windsurf — See Windsurf MCP docs for more info
• Toolset — MCP VictoriaTraces provides numerous tools for interacting with your VictoriaTraces instance
• Prompts — These are just examples at the moment, the prompt library will be added to in the future:

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 7 environment variables: VT_INSTANCE_ENTRYPOINT, VT_INSTANCE_BEARER_TOKEN, VT_INSTANCE_HEADERS, MCP_SERVER_MODE, MCP_SSE_ADDR, VT_DEFAULT_TENANT_ID, YOUR_VT_BEARER_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• VictoriaTraces instance: (single-node or cluster) - Go 1.25 or higher (if you want to build from source)

When to reach for it

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — documentation, services, service_names and 9 more — is a fair guide to whether it matches your workflow. It is maintained by VictoriaMetrics-Community; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.