Observability MCP Server

What the code does

We read the source, 6 h ago · rules 995398eba69f

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.

Connect this server

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": {
      "command": "npx",
      "args": [
        "-y",
        "@thotischner/observability-mcp"
      ]
    }
  }
}

[mcp_servers.observability-mcp]
command = "npx"
args = ["-y", "@thotischner/observability-mcp"]

{
  "mcpServers": {
    "observability-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@thotischner/observability-mcp"
      ]
    }
  }
}

{
  "servers": {
    "observability-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@thotischner/observability-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: 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)).