Skip to main content
Glama
lukleh

mcp-read-only-grafana

by lukleh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-read-only-grafana

No user-submitted related servers found.

    Related Servers

    • Grafana MCP

      izaitsevfb
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Grafana that provides tools to interact with dashboards, data sources, alerts, and more.
      1
      -

    • grafana-mcp

      daanrongen
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Grafana enabling management of dashboards, datasources, alert rules, folders, and annotations via stdio.
      3 npm
      MIT

    • mcp-grafana

      romaine-life
      F
      license
      Not graded
      quality
      D
      maintenance
      In-cluster MCP server for read-only diagnostics of Grafana, Prometheus, Alertmanager, and Loki, enabling metric queries, alert listings, and log queries through Grafana datasource proxies with Kubernetes RBAC authentication.
      -

    • Grafana MCP Server

      DrDroidLab
      A
      license
      A
      quality
      D
      maintenance
      A server that enables AI assistants to access and query Grafana dashboards, metrics, logs, and configurations through an MCP protocol interface.
      10
      6
      MIT

    • grafana-mcp

      ninanung
      A
      license
      Not graded
      quality
      D
      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.
      22 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (dashboards vs alerts vs datasources vs users). Some overlap exists: get_dashboard vs get_dashboard_info vs get_dashboard_panels and get_ruler_group vs get_alert_rules_with_state could confuse agents, though descriptions help differentiate.

    Naming Consistency3/5

    Names generally follow a verb_noun pattern (list_, get_, query_, explore_), but inconsistencies exist: get_ruler_rules vs list_alerts (same domain), get_alert_rules_with_state vs get_firing_alerts (semantic overlap), and get_dashboard_panels vs get_dashboard_panel (plural/singular ambiguity). The pattern is recognizable but not fully consistent.

    Tool Count4/5

    29 tools is on the higher end but justified for a comprehensive Grafana read-only MCP covering dashboards, alerts, datasources, queries, and admin. It feels slightly heavy but each tool addresses a distinct API endpoint or workflow need; not excessive given the platform's breadth.

    Completeness4/5

    Covers major read-only Grafana surfaces: dashboards, folders, alerts, datasources, queries (Prometheus, Loki, Explore), users, teams, annotations. Missing some common read-only endpoints like org details, notification policies, or snapshot listing, but the core operations for monitoring and exploration are well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources