"Grafana" matching MCP servers:

Enables AI agents to read Grafana dashboards, alert rules, and query datasources (Prometheus, Loki, etc.) through MCP tools, integrating Grafana monitoring into the IDE.

Gives AI coding agents read-only access to Grafana's Loki logs, Prometheus metrics, Tempo traces and active alerts from within a project, using per-project context declared in the repo and one-command switching between test and prod environments. Credentials are discovered by parsing shell rc files directly, so it works even when spawned as a non-interactive MCP client process.

This MCP server connects GitLab projects and merge requests with Jira work tracking, Confluence pages, and Grafana dashboards. It provides read-only access to GitLab, Confluence, and Grafana, while Jira mutations require explicit confirmation.

Enables natural-language queries to Tactical RMM, GLPI/TurboDesk, Zabbix, and Grafana for IT alerts, agents, tickets, problems, and dashboard metadata through a local MCP stdio server.

Enables read-only querying of a local Grafana Loki instance, providing log search, service listing, and health check capabilities.

Read-only MCP server for Grafana Loki: lets AI agents (Claude Code, Cursor, Copilot) discover labels, read bounded LogQL pages, count lines by label or time, and export logs — across several Loki stands

Exposes homelab and IT-ops tools to Claude, including system health monitoring, Grafana alert states, Docker container status, Loki logs, SMART disk health, and more.

Enables incident responders to query and correlate observability and DevOps evidence across Grafana, Prometheus, Loki, Uptime Kuma, CloudWatch, IAM, and PostHog from a local MCP client, with bounded reads and redacted audit records.