Simple Loki MCP Server
by
Provides an MCP interface for querying Grafana Loki logs via `logcli` or the Loki HTTP API, enabling AI assistants to retrieve and analyze log data directly from Loki.
Simple Loki MCP Server Overview
What is Simple Loki MCP Server about?
Simple Loki MCP Server offers an MCP endpoint that lets AI assistants execute LogQL queries, fetch label information, and receive results in various formats. It automatically chooses between the logcli CLI and the Loki HTTP API, so it works in environments where the CLI may not be installed.
How to use Simple Loki MCP Server?
- Installation
Via Smithery:
Via npm:npx -y @smithery/cli install @ghrud92/simple-loki-mcp --client claudegit clone https://github.com/ghrud92/loki-mcp.git cd loki-mcp npm install npm run build - Start the server
npm start # production npm run dev # development with hot‑reload - MCP configuration – add the server to your MCP client configuration:
Required environment variables (or a{ "mcpServers": { "simple-loki": { "command": "npx", "args": ["-y", "simple-loki-mcp"], "env": { "LOKI_ADDR": "https://your-loki-instance" } } } }logcli-config.yamlfile) includeLOKI_ADDR, optional auth variables such asLOKI_USERNAME,LOKI_PASSWORD,LOKI_BEARER_TOKEN, etc.
Key Features
- Full LogQL support through
logcliwhen available. - Automatic fallback to the Loki HTTP API if
logcliis missing. - Retrieve label values and the complete label set.
- Multiple output formats: default table, raw text, JSON‑lines.
- Rich authentication options: basic auth, bearer token, TLS certificates, multi‑tenant/organization IDs.
- Configurable via environment variables or a
logcli-config.yamlfile.
Use Cases
- AI‑driven incident investigation – let an assistant query recent error logs to pinpoint failure origins.
- Automated monitoring dashboards – generate dynamic log snapshots for dashboards without manual CLI calls.
- Security auditing – fetch logs matching suspicious patterns and feed them to analysis tools.
- Development debugging – retrieve logs for a specific service or label during CI/CD pipelines.
- Multi‑tenant SaaS platforms – isolate queries per tenant using
LOKI_TENANT_ID.
FAQ
Q: Do I need to install logcli?
A: No. The server detects its presence; if absent, it seamlessly switches to the HTTP API.
Q: Which environment variables are mandatory?
A: At minimum LOKI_ADDR (the Loki endpoint). Authentication variables depend on your Loki setup.
Q: Can I customize the query limit?
A: Yes, using the limit parameter in the query-loki tool or by setting LOKI_DEFAULT_LIMIT in a config file.
Q: How are results formatted?
A: Choose default (table), raw (plain text), or jsonl (JSON lines) via the output parameter.
Q: Is the server compatible with other MCP clients?
A: Absolutely – any client that follows the Model Context Protocol can invoke the defined tools (query-loki, get-label-values, get-labels).
Simple Loki MCP Server's README
Simple Loki MCP Server
Loki MCP Server is a Model Context Protocol (MCP) interface for querying Grafana Loki logs using logcli. The server enables AI assistants to access and analyze log data from Loki directly.
Features
- Query Loki logs with full LogQL support
- Get label values and metadata
- Authentication and configuration support via environment variables or config files
- Provides formatted results in different output formats (default, raw, JSON lines)
- Automatic fallback to HTTP API when
logcliis not available in the environment
Prerequisites
- Node.js v16 or higher
- TypeScript
- (Optional) Grafana Loki logcli installed and accessible in your PATH. If
logcliis not available, the server will automatically use the Loki HTTP API instead - Access to a Loki server instance
Installation
Installing via Smithery
To install Simple Loki MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ghrud92/simple-loki-mcp --client claude
for MCP
{
"mcpServers": {
"simple-loki": {
"command": "npx",
"args": ["-y", "simple-loki-mcp"],
"env": {
"LOKI_ADDR": "https://loki.sup.band"
}
}
}
}
npm
- Clone the repository:
git clone https://github.com/ghrud92/loki-mcp.git
cd loki-mcp
- Install dependencies:
npm install
- Build the project:
npm run build
Available MCP Tools
query-loki
Query logs from Loki with filtering options.
Parameters:
query(required): Loki query string (LogQL)from: Start timestamp (e.g. "2023-01-01T12:00:00Z")to: End timestamp (e.g. "2023-01-01T13:00:00Z")limit: Maximum number of logs to returnbatch: Batch size for query resultsoutput: Output format ("default", "raw", or "jsonl")quiet: Suppress query metadataforward: Display results in chronological order
get-label-values
Retrieve all values for a specific label.
Parameters:
label(required): Label name to get values for
get-labels
Retrieve all available labels.
No parameters required.
Configuration
You can configure Loki access using:
Environment Variables
LOKI_ADDR: Loki server address (URL)LOKI_USERNAME: Username for basic authLOKI_PASSWORD: Password for basic authLOKI_TENANT_ID: Tenant ID for multi-tenant LokiLOKI_BEARER_TOKEN: Bearer token for authenticationLOKI_BEARER_TOKEN_FILE: File containing bearer tokenLOKI_CA_FILE: Custom CA file for TLSLOKI_CERT_FILE: Client certificate file for TLSLOKI_KEY_FILE: Client key file for TLSLOKI_ORG_ID: Organization ID for multi-org setupsLOKI_TLS_SKIP_VERIFY: Skip TLS verification ("true" or "false")LOKI_CONFIG_PATH: Custom path to config fileDEBUG: Enable debug logging
Note: When the client is using the HTTP API mode (when
logcliis not available), the same configuration parameters are used to authenticate and connect to the Loki server.
Config Files
Alternatively, create a logcli-config.yaml file in one of these locations:
- Custom path specified by
LOKI_CONFIG_PATH - Current working directory
- Your home directory (
~/.logcli-config.yaml)
Example config file:
addr: https://loki.example.com
username: user
password: pass
tenant_id: mytenant
Usage
Start the server:
npm start
For development:
npm run dev
Implementation Details
Automatic Fallback to HTTP API
The server will automatically check if logcli is installed and available in the environment:
- If
logcliis available, it will be used for all queries, providing the full functionality of the CLI tool - If
logcliis not available, the server will automatically fall back to using the Loki HTTP API:- No additional configuration is needed
- The same authentication parameters are used for the HTTP API
- Response formatting is consistent with the CLI output
- Default limit of 1000 logs per query is applied in both modes
This automatic detection ensures that the server works seamlessly in different environments without manual configuration.
Development
# Run linter
npm run lint
# Fix linting issues
npm run lint:fix
# Run tests
npm run test
License
This project is licensed under the MIT License - see the LICENSE.md file for details.
Simple Loki MCP Server Reviews
Login Required
Please log in to share your review and rating for this MCP.
Actions
Simple Loki MCP Server's Information
- Author
- ghrud92
- Category
- Monitoring & Observability
- Language
- TypeScript
- License
- MIT License
- Version
- v0.0.9
- Stars
- 4
- Updated
- 2 months ago
Configuration
{
"mcpServers": {
"simple-loki": {
"command": "npx",
"args": [
"-y",
"simple-loki-mcp"
],
"env": {
"LOKI_ADDR": "<YOUR_LOKI_ADDRESS>"
}
}
}
}Claude Code (Terminal)
claude mcp add simple-loki npx -y simple-loki-mcpConfigure Clients
Similar MCP Servers like Simple Loki MCP Server
Explore related MCPs that share similar capabilities and solve comparable challenges
Netdata
by netdata
Delivers real‑time, per‑second infrastructure monitoring with zero‑configuration agents, on‑edge machine‑learning anomaly detection, and built‑in dashboards.
Phoenix
Officialby Arize-ai
Open-source AI observability platform enabling tracing, evaluation, dataset versioning, experiment tracking, prompt management, and interactive playground for LLM applications.
Tianji
by msgbyte
Provides integrated website traffic analysis, uptime checking, and server health monitoring in a single self‑hosted platform.
Grafana MCP Server
by grafana
Provides programmatic access to a Grafana instance and its surrounding ecosystem through the Model Context Protocol, enabling AI assistants and other clients to query and manipulate dashboards, datasources, alerts, incidents, on‑call schedules, and more.
Dynatrace MCP Server
by dynatrace-oss
Provides a local server that enables real‑time interaction with the Dynatrace observability platform, exposing tools for querying data, retrieving problems, sending Slack notifications, and integrating AI assistance.
Logfire MCP Server
by pydantic
Provides tools to retrieve and query OpenTelemetry trace and metric data from Pydantic Logfire, allowing LLMs to analyze distributed traces and run arbitrary SQL queries against telemetry records.
VictoriaMetrics MCP Server
by VictoriaMetrics-Community
Provides a Model Context Protocol server exposing read‑only VictoriaMetrics APIs, enabling seamless monitoring, observability, and automation through AI‑driven assistants.
Datadog MCP Server
by GeLi2001
Enables interaction with the Datadog API through a Model Context Protocol server, providing access to monitors, dashboards, metrics, logs, events, and incident data.
Last9 MCP Server
by last9
Provides AI agents with real‑time production context—including logs, metrics, traces, and alerts—through a Model Context Protocol server, enabling automatic code fixing and faster debugging.