Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

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.

README.md

LGTM MCP Server

MCP server providing read-only access to Loki, Prometheus, and Tempo APIs.

Features

  • Multi-instance support: Configure multiple LGTM stacks and switch between them
  • Bearer token authentication: Works with Grafana Cloud and self-hosted deployments
  • Query tools: Execute LogQL, PromQL, and TraceQL queries
  • Metadata discovery: Expose labels, metrics, and tags as MCP resources
  • Syntax documentation: Built-in query language references
  • OpenTelemetry tracing: All HTTP client calls are traced and exported via OTLP/gRPC

Configuration

Create a config file at ~/.config/lgtm-mcp/config.yaml:

version: "1"
default_instance: "local"

instances:
  local:
    loki:
      url: "http://localhost:3100"
    prometheus:
      url: "http://localhost:9090"
    tempo:
      url: "http://localhost:3200"

  grafana-cloud:
    loki:
      url: "https://logs-prod-us-west-0.grafana.net"
      username: "${GRAFANA_CLOUD_LOKI_USERNAME}"
      token: "${GRAFANA_CLOUD_TOKEN}"
    prometheus:
      url: "https://prometheus-prod-01-us-west-0.grafana.net/api/prom"
      username: "${GRAFANA_CLOUD_PROMETHEUS_USERNAME}"
      token: "${GRAFANA_CLOUD_TOKEN}"
    tempo:
      url: "https://tempo-prod-us-west-0.grafana.net"
      username: "${GRAFANA_CLOUD_TEMPO_USERNAME}"
      token: "${GRAFANA_CLOUD_TOKEN}"

Environment variables are expanded using ${VAR} syntax.

For Grafana Cloud, a token with read-only permissions is sufficient. See Creating access policies for details.

Usage

Claude Code

Add the MCP server using the Claude Code CLI:

claude mcp add lgtm -- uvx --from git+https://github.com/pokgak/lgtm-mcp lgtm-mcp

Or manually add to your Claude Code MCP settings (~/.claude/settings.json):

{
  "mcpServers": {
    "lgtm": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/pokgak/lgtm-mcp", "lgtm-mcp"]
    }
  }
}

Claude Desktop

Add to your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "lgtm": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/pokgak/lgtm-mcp", "lgtm-mcp"]
    }
  }
}

Local Development

If you've cloned the repository locally:

{
  "mcpServers": {
    "lgtm": {
      "command": "uv",
      "args": ["run", "lgtm-mcp"],
      "cwd": "/path/to/lgtm-mcp"
    }
  }
}

Available Tools

Loki (Logs)

  • loki_patterns - Start here! Detect log patterns and frequency (requires pattern_ingester enabled)
  • loki_stats - Get quick stats (stream count, bytes) without fetching logs
  • loki_volume - Get log volume breakdown by labels
  • loki_query_logs - Retrieve log entries (use after patterns to get specific examples)
  • loki_instant_query - Metric-type LogQL at single point
  • loki_get_labels - List label names
  • loki_get_label_values - Get values for a label
  • loki_get_series - Find matching log streams

Prometheus (Metrics)

  • prometheus_instant_query - Execute PromQL instant query
  • prometheus_range_query - Execute PromQL range query (broken)
  • prometheus_range_query_chart - Range query with ASCII chart visualization
  • prometheus_get_metric_names - List metrics
  • prometheus_get_label_names - List label names
  • prometheus_get_label_values - Get values for a label
  • prometheus_get_series - Find matching series
  • prometheus_get_metadata - Get metric metadata

Tempo (Traces)

  • tempo_trace_summary - Start here! Get trace summary with stats (duration p50/p95/p99, error count, span tree)
  • tempo_get_trace - Retrieve full trace data (use after summary for details)
  • tempo_search_traces - Search with TraceQL
  • tempo_get_tag_names - List tag names
  • tempo_get_tag_values - Get values for a tag
  • tempo_get_services - List service names

Utility

  • list_instances - List configured instances
  • set_default_instance - Change default instance

Available Resources

Resources expose metadata for query generation:

  • lgtm://{instance}/loki/labels - Loki label names
  • lgtm://{instance}/prometheus/labels - Prometheus label names
  • lgtm://{instance}/prometheus/metrics - Metric names
  • lgtm://{instance}/tempo/tags - Tempo tag names
  • lgtm://syntax/logql - LogQL syntax reference
  • lgtm://syntax/promql - PromQL syntax reference
  • lgtm://syntax/traceql - TraceQL syntax reference

Tracing

The server automatically instruments all HTTP client calls with OpenTelemetry. Traces are exported via OTLP/gRPC.

By default, traces are sent to http://localhost:4317. Override with:

export OTEL_EXPORTER_OTLP_ENDPOINT="http://your-collector:4317"

Service name: lgtm-mcp

Development

# Install with dev dependencies
uv pip install -e ".[dev]"

# Run type checks
mypy src/

# Run linter
ruff check src/

# Run tests
pytest

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Observability servers.