MCP Server for Jaeger
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jaeger-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP Server for Jaeger.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / analytics
MCP server for using the GitLab API
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
Enhanced MCP server for GitLab: group projects listing and activity tracking
MCP Security Weekly
Get CVE alerts and security updates for Jaeger Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
{
"servers": {
"jaeger-mcp-server": {
"command": "npx",
"args": ["-y", "jaeger-mcp-server"],
"envFile": "${workspaceFolder}/.env"
}
}
}
{
"mcpServers": {
"jaeger-mcp-server": {
"command": "npx",
"args": ["-y", "jaeger-mcp-server"],
"env": {
"JAEGER_URL": "<YOUR_JAEGER_HTTP_OR_GRPC_API_URL>"
}
}
}
}
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 <Basic Auth Header>)JAEGER_PROTOCOL: API protocol of the Jaeger instance to access. Valid values are GRPC and HTTP. The default value is GRPC. Validget-operations: Gets the operations as JSON array of object with name and spanKind properties.
Supports the following input parameters:
service:
Mandatory: trueType: stringDescription: Filters operations by service namespanKind:
Mandatory: falseType: stringDescription: 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: trueType: stringDescription: Filters spans by OpenTelemetry compatible trace id in 32-character hexadecimal string formatstartTime:
Mandatory: falseType: stringDescription: The start time to filter spans in the RFC 3339, section 5.6 format, (e.g., 2017-07-21T17:32:28Z)endTime:
Mandatory: falseType: stringDescription: The end time to filter spans in the RFC 3339, section 5.6 format, (e.g., 2017-07-21T17:32:28Z)find-traces: Searches the spans as JSON array of object in the OpenTelemetry resource spans format.
serviceName:
Mandatory: trueType: stringDescription: Filters spans by OpenTelemetry compatible trace id in 32-character hexadecimal string formatoperationName:
Mandatory: falseType: stringDescription: The start time to filter spans in the RFC 3339, section 5.6 format, (e.g., 2017-07-21T17:32:28Z)attributes:
Mandatory: false
Type: map<string, string | number | boolean>
Description: Filters spans by span attributes. Attributes can be passed in key/value format in JSON where
keys can be string and values can be string, number (integer or double) or boolean.
For example
{
"stringAttribute": "str",
"integerAttribute": 123,
"doubleAttribute": 123.456,
"booleanA