MCP.so
ログイン

Jaeger MCP Server

@serkan-ozal

Jaeger MCP Server について

MCP Server for Jaeger

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

serkan-ozal

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "jaeger-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "jaeger-mcp-server"
      ],
      "env": {
        "JAEGER_URL": "<YOUR_JAEGER_HTTP_OR_GRPC_API_URL>"
      }
    }
  }
}

ツール

4

Gets the operations as JSON array of object with `name` and `spanKind` properties.

Gets the service names as JSON array of string.

Gets the spans by the given trace by ID as JSON array of object in the OpenTelemetry resource spans format.

Searches the spans as JSON array of object in the OpenTelemetry resource spans format.

概要

What is Jaeger MCP Server?

Jaeger MCP Server is a Model Context Protocol (MCP) server that provides MCP-compatible tools for querying and retrieving distributed tracing data from a Jaeger instance. It is intended for developers using MCP-capable AI assistants (such as VS Code, Claude, Cursor, Windsurf, or GitHub Copilot) who need to inspect traces, services, and operations within their Jaeger deployment.

How to use Jaeger MCP Server?

Add the server to your MCP client’s configuration using the npx -y jaeger-mcp-server command. Configure the mandatory JAEGER_URL environment variable (plus optional JAEGER_PORT, JAEGER_PROTOCOL, or JAEGER_AUTHORIZATION_HEADER) either via an env block or an env file. The server uses STDIO transport and requires Node.js 18 or higher.

Key features of Jaeger MCP Server

  • Retrieves Jaeger service names and operation names.
  • Fetches an entire trace by its 32-character hexadecimal trace ID.
  • Searches for traces with filters on service, operation, attributes, time windows, and duration.
  • Supports both Jaeger HTTP JSON API (/api/v3/*) and gRPC/Protobuf API (jaeger.api_v3.QueryService).
  • Easy integration with any MCP client via a single NPM command.

Use cases of Jaeger MCP Server

  • Debug a production incident by asking an AI assistant to fetch a specific trace ID from Jaeger.
  • Explore which services and operations exist in your distributed system without switching tools.
  • Filter and find traces by custom span attributes (strings, numbers, booleans) to isolate problematic requests.
  • Query traces within a precise time range to correlate with deployment or alert windows.

FAQ from Jaeger MCP Server

What prerequisites are needed?

Node.js 18 or later must be installed on the machine running the MCP client.

How do I configure the Jaeger connection?

Set the JAEGER_URL environment variable to your Jaeger HTTP or gRPC API endpoint. Optionally set JAEGER_PORT, JAEGER_PROTOCOL (defaults to GRPC), or JAEGER_AUTHORIZATION_HEADER.

What tools does the server expose?

It exposes four tools: get-services, get-operations, get-trace, and find-traces. Each can be called by the MCP client with the documented input parameters.

Does it support both HTTP and gRPC transport?

Yes. You can choose between HTTP JSON (/api/v3/*) and gRPC/Protobuf (jaeger.api_v3.QueryService) protocols by setting the JAEGER_PROTOCOL environment variable to HTTP or GRPC.

Where can I report issues or contribute?

Issues and pull requests are handled on the project’s GitHub repository at serkan-ozal/jaeger-mcp-server. The project is licensed under MIT.

コメント

「その他」の他のコンテンツ