OpenTelemetry is an observability framework for cloud-native software. It provides tools, APIs, and SDKs to capture telemetry data from applications and process it for understanding their behavior and performance.
Enables access and analysis of OpenTelemetry traces and metrics data stored in Logfire, with tools for finding exceptions, retrieving trace information, and executing SQL queries against telemetry data.
A Model Context Protocol server that enables LLMs to retrieve and analyze OpenTelemetry traces and metrics from Logfire, supporting exception tracking and custom SQL queries against telemetry data.
Last updated
4
161
MIT
Why this server?
Core integration that emits OpenTelemetry traces, metrics, and logs to OTLP endpoints, supporting all three OTLP wire formats (gRPC, HTTP/protobuf, HTTP/JSON) for comprehensive observability data collection.
An MCP server that emits OpenTelemetry traces, metrics, and logs to OTLP endpoints in various formats. It includes tool-mimicry profiles to generate realistic traffic resembling common tools like nginx, postgres, and AWS Lambda for testing and demonstration purposes.
Last updated
11
MIT
Why this server?
Provides tools to access and search OpenTelemetry documentation, allowing users to fetch documentation pages in markdown format and search for specific content about tracing, metrics, instrumentation, and SDK configuration.
Enables access to OpenTelemetry documentation by fetching and converting pages to markdown format and searching content using Google Custom Search. Provides comprehensive documentation lookup and search capabilities for OpenTelemetry concepts, instrumentation, and configuration.
Last updated
2
3
Apache 2.0
Why this server?
Provides documentation, best practices, and configuration guidance for OpenTelemetry observability framework.
Self-hosted MCP server for live documentation, code audits, and best practices. 10 tools, unlimited library coverage (363+ curated + npm/PyPI/crates.io/Go fallback), no rate limits. Context7 alternative.
Last updated
14
199
3
Elastic 2.0
Why this server?
Supports including OpenTelemetry as a component in architecture diagrams.
Generates Excalidraw architecture diagrams with support for 60+ components including GCP, Kafka, and AI/Agentic shapes. Provides MCP tools for creating, modifying, and converting diagrams from structured input or Mermaid syntax.
Last updated
4
1
MIT
Why this server?
Integrates native OpenTelemetry support for monitoring and distributed tracing, with automatic traceparent header propagation from MCP requests.
An MCP server that gives your IDE or agent access to Google Gemini with autonomous codebase exploration, enabling deep code analysis, architectural reviews, and bug hunting.
Last updated
20
9
MIT
Why this server?
Provides performance monitoring and metrics collection through an OpenTelemetry-compatible system for tracking tool utilization and provider performance.
An MCP server that enables multi-provider AI collaboration using models like DeepSeek, OpenAI, and Anthropic through strategies such as parallel execution and consensus building. It provides specialized tools for side-by-side content comparison, quality review, and iterative refinement across different AI providers.
Last updated
4
1
MIT
Why this server?
Supplies documentation and configuration standards for integrating OpenTelemetry observability within agent architectures.
Provides standards documentation and validation tools for the Darwin platform, including naming conventions and agent card validation. It enables AI agents to search platform standards and access resource templates for design and implementation.
Last updated
6
Why this server?
Provides tools for querying and analyzing OpenTelemetry traces, allowing AI agents to list recent traces, get span trees, search spans, and get service summaries.
