SO

serkan-ozal/jaeger-mcp-server

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

18 stars 10 forks Качество 61 Тренд 22MIT

MCP Server for Jaeger

Обзор

This MCP server (using STDIO transport) can be added to any MCP Client like VS Code, Claude, Cursor, Windsurf Github Copilot via the jaeger-mcp-server NPM package. - JAEGER_URL: HTTP API (HTTP JSON (/api/v3/*)) or the gRPC API (gRPC/Protobuf (jaeger.api_v3.QueryService)) URL of the Jaeger instance to access. - JAEGER_PORT: HTTP or gRPC API port of the Jaeger instance to access. The default value is 16685 for the gRPC API and 16686 for the HTTP API. - JAEGER_AUTHORIZATION_HEADER: Authorization HTTP header to be added into the requests for querying traces over Jaeger API (for ex. Basic ) - JAEGER_PROTOCOL: API protocol of the Jaeger instance to access. Valid values are GRPC and HTTP. The default value is GRPC. Valid - get-operations: Gets the operations as JSON array of object with name and spanKind properties.

README

Показан фрагмент оригинального README. Открыть оригинал.

Jaeger MCP Server

MCP Server for Jaeger.

Prerequisites

  • Node.js 18+

Quick Start

This MCP server (using STDIO transport) can be added to any MCP Client like VS Code, Claude, Cursor, Windsurf Github Copilot via the jaeger-mcp-server NPM package.

VS Code

{
  "servers": {
    "jaeger-mcp-server": {
      "command": "npx",
      "args": ["-y", "jaeger-mcp-server"],
      "envFile": "${workspaceFolder}/.env"
    }
  }
}

Claude Desktop

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

Configuration

Environment Variables

  • JAEGER_URL: HTTP API (HTTP JSON (/api/v3/*)) or the gRPC API (gRPC/Protobuf (jaeger.api_v3.QueryService)) URL of the Jaeger instance to access.
  • JAEGER_PORT: HTTP or gRPC API port of the Jaeger instance to access. The default value is 16685 for the gRPC API and 16686 for the HTTP API.
  • JAEGER_AUTHORIZATION_HEADER: Authorization HTTP header to be added into the requests for querying traces over Jaeger API (for ex. Basic )
  • JAEGER_PROTOCOL: API protocol of the Jaeger instance to access. Valid values are GRPC and HTTP. The default value is GRPC. Valid

Components

Tools

  • get-operations: Gets the operations as JSON array of object with name and spanKind properties. Supports the following input parameters:
    • service:
      • Mandatory: true
      • Type: string
      • Description: Filters operations by service name
    • spanKind:
      • Mandatory: false
      • Type: string
      • Description: Filters operations by OpenTelemetry span kind (server, client, producer, consumer, internal)
  • get-services: Gets the service names as JSON array of string. No input parameter supported.
  • get-trace: Gets the spans by the given trace by ID as JSON array of object in the OpenTelemetry resource spans format.
    • traceId:
      • Mandatory: true
      • Type: string
      • Description: Filters spans by OpenTelemetry compatible trace id in 32-character hexadecimal string format
    • startTime:
      • Mandatory: false
      • Type: string
      • Description: The start time to filter spans in the RFC 3339, section 5.6 format, (e.g., 2017-07-21T17:32:28Z)
    • endTime:
      • Mandatory: false
      • Type: string
      • Description: The end time to filter spans in the RFC 3339, section 5.6 format, (e.g., 2017-07-21T17:32:28Z)
Открыть полный README на GitHub

Установка

npx -y jaeger-mcp-server
Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

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