MCP server for OpenTelemetry trace analysis during development
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"otel-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OTEL MCP Server An MCP (Model Context Protocol) server for Jaeger trace analysis during development. Query and analyze distributed traces with AI assistance for debugging and performance optimization. ## Features - **Service Discovery**: List services and operations in your Jaeger instance - **Trace Inspection**: Search, filter, and inspect traces with full span details - **Performance Analysis**: Find slow traces, get latency percentiles, error rates - **REST API**: FastAPI endpoints with OpenAPI documentation at `/docs` - **Self-Telemetry**: The server traces itself to Jaeger for debugging ## Installation ### Using uvx (Recommended) Run directly without installing: ```bash # Run MCP server uvx otel-mcp # Run REST API uvx --from otel-mcp otel-mcp-api ``` ### Using pip ```bash pip install otel-mcp # Then run otel-mcp # MCP server otel-mcp-api # REST API ``` ### From Source ```bash git clone https://github.com/ryanm101/otel-mcp.git cd otel-mcp uv sync uv run otel-mcp ``` ## Quick Start ### 1. Start Jaeger ```bash docker-compose up -d # Jaeger UI at http://localhost:16686 ``` ### 2. Run the MCP Server ```bash uvx otel-mcp # Or with environment variables: JAEGER_URL=http://jaeger:16686 uvx otel-mcp ``` ### 3. Or Run the REST API ```bash uvx --from otel-mcp otel-mcp-api # OpenAPI docs at http://localhost:8000/docs ``` ## MCP Client Configuration Add to your MCP client config (e.g., Claude Desktop `claude_desktop_config.json`): ```json { "mcpServers": { "otel-mcp": { "command": "uvx", "args": ["otel-mcp"], "env": { "JAEGER_URL": "http://localhost:16686" } } } } ``` ## Configuration Create a `.env` file (see `.env.example`): ```env JAEGER_URL=http://localhost:16686 JAEGER_TIMEOUT=30 LOG_LEVEL=INFO # Debug logging (writes to file in working directory) # DEBUG_LOG_FILE=otel-mcp.log # Self-telemetry (optional) OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317 OTEL_SERVICE_NAME=otel-mcp # OTE…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.