MCP server for querying Loki logs via logcli
If you already use Simple Loki MCP, the simple loki mcp mcp server is the piece that lets your assistant work with it directly. MCP server for querying Loki logs via logcli.
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.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: LOKI_ADDR, LOKI_TENANT_ID, LOKI_BEARER_TOKEN, LOKI_ORG_ID, LOKI_CONFIG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
logcli is not available, the server will automatically use the Loki HTTP API instead - Access to a Loki server instancePlenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by ghrud92; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
### for MCP
```json
{
"mcpServers": {
"simple-loki": {
"command": "npx",
"args": ["-y", "simple-loki-mcp"],
"env": {
"LOKI_ADDR": "https://loki.sup.band"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
logcli is not available, the server will automatically use the Loki HTTP API instead - Access to a Loki server instance| Variable | Description | Required |
|---|---|---|
| LOKI_ADDR | Configuration value read at startup. | Optional |
| LOKI_TENANT_ID | Configuration value read at startup. | Optional |
| LOKI_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| LOKI_ORG_ID | Configuration value read at startup. | Optional |
| LOKI_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.