Skip to main content
Glama
Jason-Shi-1

grafana-mcp

by Jason-Shi-1

Related Servers

Alternatives to grafana-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Grafana that provides tools to interact with dashboards, data sources, alerts, and more.
      1
      -
    • 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
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to interact with Grafana instances for searching, creating, and updating dashboards, exploring logs via Loki, querying datasources, managing alerts, incidents, and on-call shifts, and accessing observability data.
      8
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for Grafana. This provides access to your Grafana instance and the surrounding ecosystem.
      3,483
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Alert, dashboard, datasource, folder, contact point, notification policy, health, query, and InfluxDB exploration tools all have clear, non-overlapping purposes. Even within alerts, single vs list tools are distinct.

    Naming Consistency4/5

    Most tools follow a verb-noun pattern with hyphens (e.g., create-alert-rule, list-dashboards). Minor inconsistencies include 'create-or-update-dashboard' using a compound verb and 'get-datasource' singular vs 'list-datasources' plural, but overall pattern is predictable.

    Tool Count4/5

    22 tools is slightly above the typical sweet spot but still reasonable for a comprehensive Grafana server. The scope covers alerts, dashboards, datasources, folders, contact points, notification policies, health, query, and InfluxDB exploration, justifying the count.

    Completeness3/5

    Core CRUD for dashboards and alerts is present, but missing create/update/delete for folders, contact points, and notification policies limits workflow completeness. InfluxDB tools are read-only. Basic querying and health checks are included.

    Maintenance

    ActivityStale
    ResponsivenessNo issues