victoriametrics/mcp-victoriatraces
Deployment & DevOpsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
The implementation of Model Context Protocol (MCP) server for 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. 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.
README
以下は原文 README の抜粋です。原文を見る。
VictoriaTraces MCP Server
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)
インストール
docker run -i --rm -e VT_INSTANCE_ENTRYPOINT -e VT_INSTANCE_BEARER_TOKEN -e VT_INSTANCE_HEADERS ghcr.io/victoriametrics-community/mcp-victoriatraces設定
{
"mcpServers": {
"victoriatraces": {
"command": "/path/to/mcp-victoriatraces",
"env": {
"VT_INSTANCE_ENTRYPOINT": "<YOUR_VT_INSTANCE>",
"VT_INSTANCE_BEARER_TOKEN": "<YOUR_VT_BEARER_TOKEN>",
"VT_INSTANCE_HEADERS": "<HEADER>=<HEADER_VALUE>,<HEADER>=<HEADER_VALUE>"
}
}
}
}