Skip to main content
Glama

Loki MCP Server

CI Release codecov Go Report Card License: MIT Stars MCP

loki-mcp-server MCP server

Query Grafana Loki logs directly from AI agents using the Model Context Protocol (MCP).

Built in Go. Enables AI-powered log analysis using LogQL.

Supports integration with:

  • Claude Desktop

  • AI agent frameworks

  • automation tools

  • DevOps workflows

Motivation

The official grafana/loki-mcp exposes a single loki_query tool, which means the LLM must already know valid label names and values before it can build a query. This project takes a different approach by providing 5 granular tools — labels, label_values, and series let the LLM discover what's available in Loki first, then construct precise query_range or query calls. The result is more accurate log retrieval with fewer wasted round-trips.

Additionally, this server enforces strict input validation (limit caps, direction validation, label name format checks, mutually exclusive auth) to surface errors early instead of forwarding bad requests to Loki.

Related MCP server: Overwatch MCP

Features

  • query_range — Execute LogQL range queries to fetch logs over a time window

  • query — Execute LogQL instant queries for point-in-time evaluation

  • labels — List all available label names

  • label_values — List values for a specific label

  • series — Find active log stream series matching a selector

Installation

Homebrew

brew install incu6us/tap/loki-mcp-server

Go install

go install github.com/incu6us/loki-mcp-server/cmd/loki-mcp-server@latest

Or build from source:

git clone https://github.com/incu6us/loki-mcp-server.git
cd loki-mcp
go build -o loki-mcp-server ./cmd/loki-mcp-server

Configuration

The server is configured entirely via environment variables, injected by the MCP client.

Variable

Required

Default

Description

LOKI_URL

yes

—

Base URL of the Loki instance

LOKI_USERNAME

no

—

Basic auth username

LOKI_PASSWORD

no

—

Basic auth password

LOKI_BEARER_TOKEN

no

—

Bearer token authentication

LOKI_TLS_SKIP_VERIFY

no

false

Skip TLS certificate verification

LOKI_TENANT_ID

no

—

X-Scope-OrgID header for multi-tenant deployments

LOKI_HTTP_TIMEOUT

no

30s

HTTP request timeout (Go duration, e.g. 10s, 1m)

MCP_HTTP_ADDR

no

—

Listen address for the streamable HTTP transport, e.g. :8080. Unset means stdio

Note: Basic auth (LOKI_USERNAME/LOKI_PASSWORD) and bearer token (LOKI_BEARER_TOKEN) are mutually exclusive.

Transports

By default the server speaks MCP over stdio, which is what Claude Code, Claude Desktop and most local clients expect.

Set MCP_HTTP_ADDR to serve the streamable HTTP transport instead, for running the server as a remote endpoint behind a proxy or gateway:

LOKI_URL=http://loki:3100 MCP_HTTP_ADDR=:8080 loki-mcp-server
# MCP endpoint: http://localhost:8080/mcp

The HTTP mode is stateless, so it can run behind a load balancer with several replicas. It carries no authentication of its own — put it behind TLS and an authenticating proxy before exposing it, and remember that whoever reaches the endpoint can read every log line the configured LOKI_URL credentials can see.

Usage with Claude Code

Add to your Claude Code MCP configuration (~/.claude.json):

{
  "mcpServers": {
    "loki-mcp-server": {
      "type": "stdio",
      "command": "/path/to/loki-mcp-server",
      "args": [],
      "env": {
        "LOKI_URL": "http://loki:3100",
        "LOKI_USERNAME": "admin",
        "LOKI_PASSWORD": "secret"
      }
    }
  }
}

Usage with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "loki-mcp-server": {
      "type": "stdio",
      "command": "/path/to/loki-mcp-server",
      "args": [],
      "env": {
        "LOKI_URL": "http://loki:3100",
        "LOKI_USERNAME": "admin",
        "LOKI_PASSWORD": "secret"
      }
    }
  }
}

Tools

query_range

Execute a LogQL range query against Loki to fetch logs over a time window.

Parameter

Type

Required

Default

Description

query

string

yes

—

LogQL query expression

start

string

no

1 hour ago

Start of time range (RFC3339 or Unix nano)

end

string

no

now

End of time range

limit

number

no

100

Max entries (max 5000)

direction

string

no

backward

forward or backward

query

Execute a LogQL instant query for point-in-time evaluation.

Parameter

Type

Required

Default

Description

query

string

yes

—

LogQL query expression

limit

number

no

100

Max entries (max 5000)

time

string

no

now

Evaluation timestamp

direction

string

no

backward

forward or backward

labels

List all available label names in Loki.

Parameter

Type

Required

Default

Description

start

string

no

6 hours ago

Start of time range

end

string

no

now

End of time range

label_values

List values for a specific label.

Parameter

Type

Required

Default

Description

label

string

yes

—

Label name

start

string

no

6 hours ago

Start of time range

end

string

no

now

End of time range

series

Find active log stream series matching a selector.

Parameter

Type

Required

Default

Description

match

string

yes

—

Stream selector (e.g. {app="nginx"})

start

string

no

6 hours ago

Start of time range

end

string

no

now

End of time range

Local Development Stack

A Docker Compose setup is included under deploy/ to spin up a full Loki environment for testing:

  • Loki — log storage at http://localhost:3100

  • Grafana — UI at http://localhost:3000 (anonymous admin, Loki pre-configured as datasource)

  • Promtail — collects container logs and ships them to Loki

  • Log generator — emits structured JSON logs with randomized apps (nginx, api, gateway, auth, payments), levels, and messages

# Start the stack
docker compose -f deploy/docker-compose.yml up -d

# Use loki-mcp-server against local Loki
LOKI_URL=http://localhost:3100 loki-mcp-server

# Stop the stack
docker compose -f deploy/docker-compose.yml down

Development

# Run tests
go test ./...

# Build
go build -o loki-mcp-server ./cmd/loki-mcp-server

# Vet
go vet ./...

⭐ If this project is useful for you, please star the repository.

Available Tools

5 tools
labelsA
Read-onlyIdempotent

List the label names Loki knows about in a time window.

Start here when the log schema is unknown: labels gives the names (app, namespace, level), then label_values gives the values for one of them, and together they let you write a valid selector for query_range. Only labels present on streams that received data inside the window are returned, so widening start/end surfaces more.

Returns the raw Loki JSON response: {"status","data":["label","names"]}. Read-only: it never writes to or mutates Loki.

Inputs: end, start.

label_valuesA
Read-onlyIdempotent

List the values a single label takes in Loki over a time window.

Use it after labels to fill in a selector: labels says "app" exists, label_values with label="app" says which apps are actually logging, and one of those goes into {app="..."} for query_range. Only values seen inside the window are returned, so widening start/end surfaces more.

Returns the raw Loki JSON response: {"status","data":["value","list"]}. An unknown label name is not an error; it comes back as an empty list. Read-only: it never writes to or mutates Loki.

Inputs: label (required), end, start.

queryA
Read-onlyIdempotent

Run a LogQL instant query against Loki, evaluating the expression at a single point in time.

Use this for metric expressions (rate, count_over_time, sum by) when one value per series is enough, or for a quick "what is happening right now" check. To read log lines across a time window, use query_range instead. To discover which labels exist before writing a selector, use labels and label_values.

Returns the raw Loki JSON response: {"status","data":{"resultType","result"}}, where resultType is "vector" for metric expressions and "streams" for log selectors. Read-only: it never writes to or mutates Loki.

Inputs: query (required), time, limit, direction.

query_rangeA
Read-onlyIdempotent

Run a LogQL range query against Loki, returning results across a time window.

This is the tool to reach for when reading logs: searching for errors, tailing a service over the last hour, or graphing a metric expression over time. Use query instead when a single point-in-time value is enough. If the selector is unknown, call labels and label_values first.

Returns the raw Loki JSON response: {"status","data":{"resultType","result"}}, where resultType is "streams" for log selectors and "matrix" for metric expressions. Loki truncates at limit entries, so a full result set may mean logs were cut off; narrow start/end or tighten the selector rather than raising limit. Read-only: it never writes to or mutates Loki.

Inputs: query (required), end, limit, start, +1 more.

seriesA
Read-onlyIdempotent

List the log streams matching a selector, as complete label sets.

Use it to see which concrete streams a selector actually covers and what other labels they carry: {app="nginx"} may expand to one series per pod, region or level. That answers "does this selector match anything" and "how many streams am I about to read" without fetching log lines. For the lines themselves, use query_range; for label names and values in isolation, use labels and label_values.

Returns the raw Loki JSON response: {"status","data":[{"label":"value"}]}, one object per stream. A selector matching nothing comes back as an empty list. Read-only: it never writes to or mutates Loki.

Inputs: match (required), end, start.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: labels lists names, label_values lists values for a given label, query runs instant queries, query_range runs range queries, and series lists matching streams. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names are in snake_case and follow a clear pattern: label_values, labels, query, query_range, series. They are consistent in style and predictable, with multi-word names clearly separated by underscores.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a log querying service. Each tool is essential and there are no redundant or excessive entries.

    Completeness5/5

    The tool surface covers the full read-only workflow for Loki: discovering labels, discovering label values, running instant queries, running range queries, and checking stream coverage. No obvious gaps for typical use cases.

    Maintenance

    ActivityStale
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      D
      quality
      D
      maintenance
      An MCP interface that allows AI assistants to query and analyze Grafana Loki logs using LogQL, with support for authentication and various output formats.
      3
      1,511 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables natural-language querying of Grafana logs by automatically detecting log sources and service labels. It provides read-only access to log data with intelligent caching for efficient repeat queries.
      98 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query and analyze logs from Grafana Loki using LogQL, supporting label discovery and keyword search.
      4
      -