Skip to main content
Glama
enrique-pastrana

grafana-mcp-adapter

by enrique-pastrana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to grafana-mcp-adapter

No user-submitted related servers found.

    Related Servers

    • Grafana FastMCP Server

      sandersouza
      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

    • 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

      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
      -

    • devops-mcp-server

      rpsangam
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes DevOps/SRE operations like Kubernetes pod status, Prometheus metrics queries, and deploy history as tools for MCP-compatible clients.
      -

    • mcp-incident-copilot

      ShreyAC962
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.
      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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct Grafana operation: health check, datasource listing, dashboard search and retrieval, general querying, and a specialized logs link builder. No functional overlap exists.

    Naming Consistency4/5

    All tools share the 'grafana_' prefix and mostly follow a verb_noun pattern (get_dashboard, list_datasources, search_dashboards). Exceptions like 'health' (noun) and 'logs_link' (noun_noun) are minor inconsistencies within an otherwise coherent scheme.

    Tool Count5/5

    With 6 tools, the server covers the essential read-only Grafana operations without being excessive. Each tool serves a clear purpose and earns its place.

    Completeness4/5

    The set covers core read-only functionality: health, datasources, dashboards, querying, and logs linking. Missing are alerting and annotations, but the surface is complete for common exploration tasks and tools are well-connected (e.g., search_dashboards feeds get_dashboard).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources