Grafana MCP SSE Server

Created By
aimioxa year ago
Grafana SSE Server provides an easy way to query Grafana dashboards and panels using the MCP — enabling natural language querying, monitoring dashboards, and real-time data extraction. sudo docker run -p 8010:8010 \ -e GRAFANA_API_KEY="YOUR_KEY" \ -e GRAFANA_URL="https://grafana.example.com" \ aimiox/amx-mcp-grafana:latest
Overview

what is Grafana MCP SSE Server?

Grafana MCP SSE Server is a tool that allows users to query Grafana dashboards and panels using the Model Context Protocol (MCP), enabling natural language querying, monitoring dashboards, and real-time data extraction.

how to use Grafana MCP SSE Server?

To use the Grafana MCP SSE Server, run the following command in your terminal:

sudo docker run -p 8010:8010 \
  -e GRAFANA_API_KEY="YOUR_KEY" \
  -e GRAFANA_URL="https://grafana.example.com" \
  aimiox/amx-mcp-grafana:latest

key features of Grafana MCP SSE Server?

  • Natural language querying of Grafana dashboards
  • Real-time data extraction from Grafana panels
  • Easy integration with Docker for deployment

use cases of Grafana MCP SSE Server?

  1. Monitoring system performance through Grafana dashboards.
  2. Extracting real-time data for analysis and reporting.
  3. Enabling users to interact with Grafana using natural language queries.

FAQ from Grafana MCP SSE Server?

  • Can I use Grafana MCP SSE Server with any Grafana instance?

Yes! As long as you have the correct API key and URL, you can connect to any Grafana instance.

  • Is there a cost associated with using Grafana MCP SSE Server?

The server is open-source and free to use.

  • What is the Model Context Protocol (MCP)?

MCP is a lightweight framework for managing and sharing contextual memory across language models in real time.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aimiox
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago