Skip to main content
Glama
UjjwalSk

Tempo MCP Server

by UjjwalSk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Tempo MCP Server

No user-submitted related servers found.

    Related Servers

    • LGTM MCP Server

      pokgak
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Loki, Prometheus, and Tempo APIs, enabling natural language queries for logs, metrics, and traces. Supports multiple instances and authentication via bearer tokens.
      1
      MIT

    • otel-mcp-server

      shiftyp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying and analysis of OpenTelemetry traces, metrics, and logs stored in Elasticsearch/OpenSearch, allowing AI assistants to investigate performance issues, find root causes, and explore system behavior.
      12 npm
      14
      MIT

    • tracehub-mcp

      mcpsmiths
      A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants to OpenTelemetry trace backends such as Jaeger, Tempo, Traceloop, and Datadog, enabling natural-language searching of traces and spans, error discovery, and service listing. It also provides LLM-specific analytics, including token usage aggregation, model performance comparison, and identification of the most expensive or slowest traces.
      17
      Apache 2.0

    • grafana-mcp-observability

      akkireddy-challa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Grafana dashboards, alerts, and datasources for observability insights and incident investigation.
      MIT

    • grafana-mcp-server

      stonoyan04
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query Grafana datasources (Prometheus/Loki metrics and SQL databases like ClickHouse/Postgres/MySQL) and search or inspect dashboards through natural language, using read-only access to Grafana's API.
      6
      MIT

    • OTEL MCP Server

      krackenservices
      A
      license
      B
      quality
      C
      maintenance
      Enables querying and analyzing distributed traces from Jaeger, including service discovery, trace inspection, and performance analysis, through MCP tools.
      7
      2
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are largely distinct: get_trace (full trace), search_traces (TraceQL), get_trace_spans (spans within a trace), search_spans (spans across traces), get_span_statistics (aggregations), query_by_tag (tag-based queries). The main overlap is between search_traces and query_by_tag—both retrieve traces—but the tool descriptions clarify their inputs. This is a modest overlap, not a severe one.

    Naming Consistency4/5

    Naming follows a consistent pattern of tempo_ followed by action_noun: tempo_get_trace, tempo_search_traces, tempo_get_trace_spans, tempo_search_spans, tempo_get_span_statistics, tempo_query_by_tag. The verb/noun structure is uniform across all tools, making the API predictable. tempo_query_by_tag uses 'query' instead of 'search', a minor deviation, but overall the pattern is clear and consistent.

    Tool Count5/5

    Six tools is a well-scoped set for a tracing query server. Each tool serves a distinct purpose: retrieving full traces, searching by query language, filtering spans, cross-trace span search, aggregations, and tag-based lookup. None feel redundant or unnecessary; the count is right for the domain scope.

    Completeness4/5

    The server covers trace lookup, searching (by TraceQL and tags), span retrieval, and statistics—a solid coverage of Tempo's core tracing query workflows. Missing operations like trace comparison or raw query execution are minor; the surface is reasonably complete for its domain. A notable gap is no direct capability to fetch recent traces without a query, relying on search having sensible defaults.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources