jaeger-mcp-server

jaeger-mcp-server

4
monitoring

The Jaeger MCP Server is a Model Context Protocol server designed to integrate with MCP clients to facilitate the querying and management of traces in a Jaeger instance. It supports configuration via environment variables and provides several tools for fetching traces, services, and operations.

Jaeger MCP Server

Build Status NPM Version License

MCP Server for Jaeger.

Prerequisites

  • Node.js 18+

Quick Start

The Jaeger MCP Server is an MCP server which can be integrated with any MCP Client such as VS Code, Claude, Cursor, Windsurf Github Copilot via the jaeger-mcp-server NPM package.

Configuration

Environment Variables

  • JAEGER_URL: URL of the HTTP API or gRPC API of the Jaeger instance.
  • JAEGER_PORT: Port of the Jaeger instance. Defaults are 16685 for gRPC API and 16686 for HTTP API.
  • JAEGER_AUTHORIZATION_HEADER: HTTP Authorization header for querying traces.
  • JAEGER_PROTOCOL: API protocol of the Jaeger instance (GRPC or HTTP). Default is GRPC.

Components

Tools

  • get-operations: Fetches operations as a JSON array of objects, filtered by service name and span kind.
  • get-services: Retrieves service names as a JSON array.
  • get-trace: Gets spans by trace ID, filtered by conditions like start and end time.
  • find-traces: Searches spans as JSON objects, filtered by service name, operation name, attributes, and time interval.

Roadmap

  • Support for HTTP Stream protocol to enable remote usage of the MCP server.
  • More tool support not directly available via Jaeger API.

Issues and Feedback

Please use GitHub Issues for bug reports and feature requests.

Contribution

If you would like to contribute, fork the repository on GitHub, create a branch, make your changes, and send a pull request.