Observability MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 324 installs a week from npm. Last commit 15 Sep 2026.
Unified observability gateway for AI agents — Prometheus, Loki & more, with anomaly detection.
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const r = spawnSync(bin, args, { encoding: "utf8" });
grid.innerHTML=out.length?out.map(card).join(""):`<div class="empty">No connectors match.</div>`;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add observability-mcp -- npx -y @thotischner/observability-mcp
{
"mcpServers": {
"observability-mcp": {
"args": [
"-y",
"@thotischner/observability-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.observability-mcp]
command = "npx"
args = ["-y", "@thotischner/observability-mcp"]
{
"mcpServers": {
"observability-mcp": {
"args": [
"-y",
"@thotischner/observability-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"observability-mcp": {
"args": [
"-y",
"@thotischner/observability-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
MCP_TRANSPORT (Set to 'stdio' when an MCP client spawns the package directly (the npx default starts the HTTP gateway + Web UI on :3000 instead).), PROMETHEUS_URL (Prometheus base URL to connect as a metrics source (optional; sources are also configurable via the Web UI / sources.yaml).), LOKI_URL (Loki base URL to connect as a logs source (optional).).
The author declared them in the registry entry; get the values from the project itself.
Agent tracing, cost tracking, anomaly detection for LLM agents
Observability for incident agents — query Loki (LogQL), Prometheus (PromQL), Elasticsearch.
Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.
Security gateway for AI agents: detects prompt injections, jailbreaks, and common vulnerabilities.
Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki
MCP server for querying logs from observability platforms with unified search and tracing
AI agent observability with deterministic record/replay for debugging agent failures.
Multi-agent observability: cascade failure detection, heartbeats, and forensic replay
Answers built from our own checks of this server.