Observability MCP Server

One MCP server that connects to any observability backend through pluggable connectors, normalizes the data, adds robust anomaly analysis, and provides a web UI for configuration. Exposed over MCP by the observability mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

The server ships on npm as @thotischner/observability-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• list_sources — meta
• list_services — meta
• query_metrics — metrics
• query_logs — logs
• get_service_health — unified
• detect_anomalies — unified
• get_topology — topology
• get_blast_radius — topology

Configuration

You will need 3 environment variables: PROMETHEUS_URL, LOKI_URL, GRAFANA_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the observability mcp mcp server does with a few real requests.

When to reach for it

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Observability MCP's toolset — list_sources, list_services, query_metrics and 5 more — is a fair guide to whether it matches your workflow. It is maintained by thotischner; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.