MCP servers · adiakys

OtlpDashboard: self-hosted OpenTelemetry dashboard with optional read-only MCP server

A self-hosted viewer that receives OpenTelemetry traces, logs and metrics over OTLP, with an optional read-only MCP server for querying them.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

OtlpDashboard receives OTLP traces, logs and metrics over gRPC and HTTP/Protobuf and shows them in a web interface. The backend is built on .NET 10 with EF Core and the frontend is a Vue 3 and Nuxt 4 single-page app. Telemetry can be stored in SQLite, PostgreSQL or SQL Server. Dashboards are assembled from widgets on a 12-column grid, including stat, line, gauge, heatmap, recent traces and log stream types.

It suits teams that want a self-hosted OpenTelemetry viewer with less setup than larger observability stacks. An optional MCP server, disabled by default, exposes the same logs, traces and metrics queries to LLM clients such as Claude Code. Retention is set per signal, with logs kept longer than traces and metrics by default.

A Docker Compose file starts the dashboard on PostgreSQL with a sample workload. For local use without Docker, the backend runs migrations on startup and creates a SQLite file. Settings are read from appsettings.json and can be overridden with environment variables. Two bearer tokens protect the browser interface, API and MCP endpoint, and OTLP ingestion respectively.

Limitations and requirements

Each token is optional. If a token is left empty, that surface is public and the dashboard reports Degraded on the health endpoint. A retention value of 0 keeps records indefinitely and also reports Degraded. The live demo runs on a mock backend and can differ from the real server. On PostgreSQL with SSD storage, the publisher recommends lowering random_page_cost to 1.1. The MCP server is read-only and must be enabled explicitly. OTLP clients must send the API key when ingestion is protected.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    OtlpDashboard

    Query OpenTelemetry logs, traces and metrics from a self-hosted OTLP dashboard

    v26.11
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026