Jaeger MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update version in pyproject.toml
        run: |
          NEW_VERSION=${{ steps.bump_version.outputs.new_version }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add jaeger-mcp -- uvx jaeger-mcp

{
  "mcpServers": {
    "jaeger-mcp": {
      "args": [
        "jaeger-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.jaeger-mcp]
command = "uvx"
args = ["jaeger-mcp"]

{
  "mcpServers": {
    "jaeger-mcp": {
      "args": [
        "jaeger-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "jaeger-mcp": {
      "args": [
        "jaeger-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: JAEGER_URL (Jaeger query service URL, e.g. https://jaeger.example.com), JAEGER_TOKEN (Bearer token for authentication. Takes priority over Basic auth.), JAEGER_USERNAME (HTTP Basic auth username. Used only when JAEGER_TOKEN is not set.), JAEGER_PASSWORD (HTTP Basic auth password.), JAEGER_SSL_VERIFY (Verify SSL certificates (true/false). Set to 'false' for self-signed certs.). The author declared them in the registry entry; get the values from the project itself.