Part of Grafana, not a vendor of its own. The four checks, setup and context cost live in the Grafana guide.
Part of the Grafana stack
Grafana's log store. Logs go in labeled by stream, and come out through LogQL, which looks like PromQL with a log filter on the end.
The main Grafana MCP server, with nothing extra to install. All seven Loki tools are on by default, so a working Grafana connection already reaches them.
query_loki_logslist_loki_label_nameslist_loki_label_valuesquery_loki_statsquery_loki_patternsanalyze_loki_labelssuggest_loki_alloy_label_configloki.process snippet enforcing an approved label set.Seven tools, all on by default, counted from the captured tools/list for the Grafana MCP server. One more tool reaches Loki without naming it: find_error_pattern_logs searches Loki for error patterns elevated against the previous period.
Grafana Cloud caps a Loki query at 500 series. With 1,800 hosts reporting, a broad aggregation returns 1,800 series and fails with an HTTP 400, not a partial result. Self-hosted Loki is not bound by that published cap; its own limit is 5,000 entries per query, set in local config.
What to do: Narrow the stream selector before widening the time range. query_loki_stats exists to tell you how many streams a selector matches before you pay for the query.
Grafana Loki is part of Grafana, not a vendor of its own
The four checks, the setup, the context cost and the read-only configuration are all decided at the Grafana level, so they live in that guide rather than being repeated here.