広告掲載
MCP.so
ログイン

Grafana MCP Server (Official)

@grafana

リポジトリ

基本情報

カテゴリ

開発者ツール

ライセンス

Apache-2.0

トランスポート

stdio

作者

grafana

Grafana MCP Server について

Grafana 用の MCP サーバー

Grafana MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "grafana": {
      "command": "uvx",
      "args": [
        "mcp-grafana"
      ],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
      }
    }
  }
}

Grafana MCP Server のツール

79

Add a note (userNote activity) to an existing incident's timeline using its ID. The note body can include URLs which will be attached as context. Use this to add context to an incident.

Manage Grafana alerting routing configuration, including notification policies, contact points and time intervals. Notification policies define how alerts are grouped, routed, and which contact points receive them. Time intervals define active/mute periods for alert notifications. When to use: - Understanding how alerts are routed to contact points/receivers - Debugging why an alert went to a specific receiver - Checking grouping, timing, or mute interval settings Does not show alert rule configuration or state.

Create Grafana-managed contact points for alert notifications using operation 'create_contact_point'. Requires name, type and integration-specific settings. Returns uid, name and type without settings or secrets. Contact points remain editable in the Grafana UI by default. External Alertmanager receivers are not supported. Does not list or inspect existing contact points.

List and inspect Grafana alert rules with filtering capabilities. When to use: - Understanding why an alert is or isn't firing - Auditing alert rule configuration (queries, conditions, labels, notification settings) - Finding alert rules by state, folder, group, or name - Comparing rule versions to see what changed Read-only: does not create, update, or delete rules, and does not show notification routing.

Create, update, and delete Grafana alert rules. When to use: - Creating, updating, or deleting alert rules Operation 'update' replaces the whole rule: it takes all required fields, not only the changed ones. Does not list or inspect rules, and does not manage notification routing.

List and inspect Grafana alerting silences. A silence temporarily suppresses notifications for alerts whose labels match a set of matchers. Operations: - 'list': list existing silences. Optionally filter by rule_uid (matches the __alert_rule_uid__ label) or by matchers. - 'get': retrieve a single silence by silence_id. When to use: - Inspecting which alerts are currently silenced and why Read-only: does not create, update, or delete silences, and does not show alert rules or notification routing.

Create, update, and delete Grafana alerting silences. A silence temporarily suppresses notifications for alerts whose labels match a set of matchers, without changing the alert rules themselves. Operations: - 'create': create a new silence. Requires matchers, starts_at, ends_at (RFC3339) and comment. - 'update': modify an existing silence by silence_id. Requires matchers, starts_at, ends_at and comment. The id is only kept when the posted matchers and starts_at match the stored ones, so pass back the stored starts_at of the silence; otherwise Alertmanager expires the old silence and returns a new id. - 'delete': expire/remove a silence by silence_id. When to use: - Muting noisy or expected alerts during maintenance windows Does not list or inspect silences, change alert rules, or manage notification routing.

Audits a Loki label strategy and optionally diagnoses query performance. Returns per-label verdicts, missing base labels, normalisation issues, and a recommended set. Pass datasourceUid for live cardinality or labels for static scoring; both may be combined.

Check datasource health. Filter by type or UIDs; omit both to check all.

Create a new annotation on a dashboard or panel. Set format to 'graphite' and provide 'what' for Graphite-format annotations.

Create a datasource in two steps. Called with only the type, it returns the plugin's field schema and creates nothing. Called with the type, the display name in the top-level name argument, schemaReviewed=true, and field values in the fields map, it creates the datasource. The plugin for the type must already be installed. Secrets (passwords, tokens) are not accepted. Returns UID, health check, and a config page link.

Create a Grafana folder. Provide a title and optional UID. Returns the created folder.

Create a new Grafana incident. Requires title, severity, and room prefix. Allows setting status, labels and custom fields. Creating an incident may notify or page many people.

Create a Grafana snapshot from a full dashboard payload. Supports optional expiration and external snapshot fields.

Permanently delete an annotation by ID. The annotation cannot be recovered afterwards.

Delete a Grafana snapshot by snapshot key.

Compare two complete traces. Returns a compact summary and includes the full span-level patch when it is at most 64 KiB. Request trace-patch-v0 only when full details are required; full patches are not size-bounded.

Generate deeplink URLs for Grafana resources. Supports dashboards (requires dashboardUid or provisioningPreview), panels (requires dashboardUid or provisioningPreview, plus panelId), and Explore queries (requires datasourceUid and optionally queries). For dashboard and panel links, provisioningPreview points at a dashboard staged on a provisioning repository branch (e.g. a git-sync PR preview). For explore links, the time range and queries are embedded inside the Grafana explore state. Set shorten=true to also attempt a /goto/<uid> short URL; if shortening fails, the full deeplink is returned.

Get a specific alert group from Grafana OnCall by its ID. Returns the full alert group details, including the most recent alert and its raw payload when the OnCall API provides them. Alert payloads carry integration-specific fingerprints (for example Sentry's payload.data.event.hashes or Alertmanager's payload.alerts[].fingerprint) that identify recurring alerts across different alert groups.

Returns annotation tags with optional filtering by tag name. Only the provided filters are applied.

Fetch Grafana annotations using filters such as dashboard UID, time range and tags.

Get assertion summary for a given entity with its type, name, env, site, namespace, and a time range

Get the list of users currently on-call for a specific Grafana OnCall schedule ID. Returns the schedule ID, name, and a list of detailed user objects for those currently on call.

Retrieves the complete dashboard, including panels, variables, and settings, for a specific dashboard identified by its UID. Pass optional version to load a saved snapshot instead of the current dashboard. Saved snapshots are fetched through Grafana's legacy versions API, so 'apiVersion' is omitted and 'meta' is partial: only version, createdBy, and created are populated. For current (non-versioned) fetches, the response includes 'apiVersion' and 'isV2': when 'isV2' is true the dashboard uses the v2 schema (panels live under 'elements' keyed by name, arranged by 'layout'; variables under 'variables'), otherwise it is classic v1 ('panels[]' with 'templating.list'). The full JSON of a large dashboard can be very large.

Retrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Optionally provide `variables` for template variable substitution, which populates `processedQuery` and `requiredVariables` fields. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, requiredVariables, and target. Targets built in a visual editor (CloudWatch metric search, InfluxDB query builder) have no string expression: those return an empty query plus `target`, the panel's raw query JSON. They can be executed as panel queries but not as standalone expressions.

Get specific parts of a dashboard using JSONPath expressions to minimize context window usage. JSONPath targets the dashboard's native schema. Classic v1 paths: '$.title' (title), '$.panels[*].title' (all panel titles), '$.panels[0]' (first panel), '$.templating.list' (variables), '$.annotations.list' (saved dashboard annotation queries/definitions), '$.tags' (tags), '$.panels[*].targets[*].expr' (all queries). v2 dashboards (isV2 true) use different paths: '$.title', '$.elements' (panels, keyed by name), '$.variables' (variables), '$.annotations'.

Get a compact summary of a dashboard including title, panel count, panel types, variables, and other metadata without the full JSON. Use this for dashboard overview and planning modifications without consuming large context windows.

Retrieves detailed information about a specific datasource by UID or name. Returns the full datasource model, including name, type, URL, access settings, JSON data, and secure JSON field status. Provide either uid or name; uid takes priority if both are given.

Fetch a Grafana documentation page. Set outline_only=true to get the heading structure first, then call again with a section name for bounded retrieval.

Get a single incident by ID. Returns the full incident details including title, status, severity, labels, custom fields, timestamps, and other metadata.

Get detailed information for a specific Grafana OnCall shift using its ID. A shift represents a designated time period within a schedule when users are actively on-call. Returns the full shift details.

Render a Grafana dashboard panel, full dashboard or Explore view as a PNG image. Returns the image as base64 encoded data. Requires the Grafana Image Renderer service to be installed. Exactly one of dashboardUid (for stored dashboards), provisioningPreview (for dashboards staged on a provisioning repository branch, e.g. a git-sync PR) or explore (an ad-hoc datasource query rendered in Explore, no saved dashboard needed) must be supplied. Use this for generating visual snapshots of dashboards for reports, alerts, or presentations.

Check whether a Grafana plugin is installed and retrieve its details (name, version, type, enabled status). Returns installed=false when the plugin is not found.

Get a Grafana snapshot by key, including snapshot metadata and dashboard payload.

Retrieve a specific trace by ID

Retrieve TraceQL reference documentation with examples, covering attribute filters, aggregates, structural operators, and metrics queries. Consult this before writing a non-trivial TraceQL query, or after one returns an error or no results.

Make an authenticated HTTP request to the Grafana API. Similar to 'gh api' for GitHub. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.

Install a Grafana plugin by its plugin ID. When version is omitted, the tool looks up the latest version and returns it without installing; supplying a version installs that version.

List alert groups from Grafana OnCall with filtering options. Supports filtering by alert group ID, route ID, integration ID, state (new, acknowledged, resolved, silenced), team ID, time range, labels, and name. For time ranges, use format '{start}_{end}' ISO 8601 timestamp range (e.g., '2025-01-19T00:00:00_2025-01-19T23:59:59' for a specific day). For labels, use format 'key:value' (e.g., ['env:prod', 'severity:high']). Returns a list of alert group objects with their details. Supports pagination.

List saved versions of a Grafana dashboard. Returns compact metadata: version number, author, timestamp, and save message. A version number can be passed to the dashboard fetch to load that snapshot.

List all configured datasources in Grafana. Use this to discover available datasources and their UIDs. Supports filtering by type and/or name (case-insensitive substring match) and pagination.

List the custom fields configured for Grafana incidents, including their type and, for select fields, the options that may be chosen.

List Grafana incidents. Allows filtering by status ('active', 'resolved') and optionally including drill incidents. Returns a preview list with basic details, and custom field values if requested.

Lists all available label/field names (keys) found in logs within a specified Loki or VictoriaLogs datasource and time range. Returns a list of unique label strings (e.g., `["app", "env", "pod"]`). If the time range is not provided, it defaults to the last hour. Optionally narrow the search to a subset of streams with `matcher` (e.g. `{namespace="prod"}`).

Retrieves all unique values associated with a specific `labelName` within a Loki or VictoriaLogs datasource and time range. Returns a list of string values (e.g., for `labelName="env"`, might return `["prod", "staging", "dev"]`). Useful for discovering filter options. Defaults to the last hour if the time range is omitted. Optionally narrow the search to a subset of streams with `matcher` (e.g. `{namespace="prod"}`) — for example, to list `service` values seen only within a specific namespace.

List Grafana OnCall schedules, optionally filtering by team ID. If a specific schedule ID is provided, retrieves details for only that schedule. Returns a list of schedule summaries including ID, name, team ID, timezone, and shift IDs. Supports pagination.

List teams configured in Grafana OnCall. Returns a list of team objects with their details. Supports pagination.

List users from Grafana OnCall. These are OnCall users (separate from Grafana users). Can retrieve all users in the OnCall directory, a specific user by ID, or filter by username. Returns a list of user objects with their details. Supports pagination.

List label names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range.

Gets the values for a specific label name in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range.

List Prometheus metric metadata. Returns metadata about metrics currently scraped from targets. Note: This endpoint is experimental.

Lists metric names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Filters metric names using the provided regex. Supports pagination (page * limit must not exceed 10000) and an optional time range to restrict results to metrics active within that window. Cloud Monitoring ignores the time range.

List provisioning repositories (e.g. git-sync sources) configured for this Grafana instance. Returns each repository's slug along with its source URL, branch, path, sync state, and health. The `name` is the slug used to render not-yet-applied dashboard previews.

Lists all available label names (keys) found in profiles within a specified Pyroscope datasource, time range, and optional label matchers. Label matchers are typically used to qualify a service name ({service_name="foo"}). Returns a list of unique label strings (e.g., ["app", "env", "pod"]). Label names with double underscores (e.g. __name__) are internal and rarely useful to users. If the time range is not provided, it defaults to the last hour.

Lists all available label values for a particular label name found in profiles within a specified Pyroscope datasource, time range, and optional label matchers. Label matchers are typically used to qualify a service name ({service_name="foo"}). Returns a list of unique label strings (e.g. for label name "env": ["dev", "staging", "prod"]). If the time range is not provided, it defaults to the last hour.

Lists all available profile types available in a specified Pyroscope datasource and time range. Returns a list of all available profile types (example profile type: "process_cpu:cpu:nanoseconds:cpu:nanoseconds"). A profile type has the following structure: <name>:<sample type>:<sample unit>:<period type>:<period unit>. Not all profile types are available for every service. If the time range is not provided, it defaults to the last hour.

List Grafana dashboard snapshots with optional query and result limit filters.

List available attribute names for TraceQL queries. Without a scope (resource, span, etc.) the response can be very large.

List values for a fully scoped attribute name (e.g. resource.service.name). Useful for discovering what values exist for a specific attribute.

Executes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app="foo"} |= "error"`; VictoriaLogs: `{app="foo"} "error"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~".*"`/`=~".+"`, or negative-only matchers), keep time ranges narrow; rejected queries return rewrite guidance.

Retrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string and a total count of occurrences. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job="nginx"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead.

Retrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. Counting actual matching log lines requires a `count_over_time()` LogQL metric query. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app="nginx", env="prod"}`) and does not support line filters, parsers, or aggregations. Defaults to the last hour if the time range is omitted.

Query a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Supports instant queries (single point) and range queries (time range). Time: RFC3339 or relative expressions like 'now', 'now-1h'.

Query Prometheus histogram percentiles from classic histogram '_bucket' series. Generates histogram_quantile PromQL. Example: metric='http_duration', percentile=95, labels='job="api"' Time formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)

Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call. query_type options (extends Grafana's PyroscopeQueryType): - "profile": returns profile data (shape controlled by format) - "metrics": returns time-series data points - "both" (default): returns both profile and metrics in one response format options (shape of the profile data): - "table" (default): per-function table with flat (self) and cumulative values, ranked by flat - "dot": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes

Compute trace-derived metrics using a TraceQL metrics query. The syntax is unlike PromQL. Use type 'instant' for a single value or 'range' for a time series (default). Instant queries over large time ranges may timeout — keep the window under 15 minutes for instant, or use range instead.

Search Grafana dashboards by query and/or folderUid, tag, and starred. Returns matching dashboards with title, UID, folder, tags, and URL.

Search Grafana documentation. Returns matching pages with title, URL, description, and product. Call with no query to list available product groups.

Search for Grafana folders by a query string. Returns matching folders with details like title, UID, and URL.

Search the Grafana plugin catalog by keyword, purpose, or partial name (e.g. 'azure monitoring', 'loki', 'database'). Returns results sorted by trust: official Grafana Labs plugins first, then commercial partner plugins, then community plugins, each with its exact pluginId. Results include warnings for enterprise-only or Angular-based plugins.

Search for traces using TraceQL queries

Generates an Alloy loki.process snippet enforcing an approved label set via stage.label_keep, with optional log-level normalisation and soft-enforcement placeholders.

Update the state of a Grafana OnCall alert group: acknowledge, unacknowledge, resolve, or unresolve it by ID. Returns the alert group's resulting OnCall state (one of new, acknowledged, resolved, silenced), or a stateWarning explaining why that state could not be read back after a successful update.

Updates the provided properties of an annotation by ID. Only fields included in the request are modified; omitted fields are left unchanged.

Create or update a dashboard. Returns the saved dashboard UID and dashboard link in the 'url' field, using the instance public URL when available. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions live in dashboard JSON under 'annotations.list'; annotation events are stored separately and are not part of the dashboard JSON. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. Schema: prefer v2 for new dashboards; if this Grafana lacks v2 the save fails saying so, then send v1. Keep an existing dashboard in its stored schema (indicated by 'isV2'/'apiVersion' on the fetched dashboard). A body with top-level 'elements'/'layout' is saved as v2. Minimal v2 body: {"title":"T","timeSettings":{"from":"now-6h","to":"now"},"variables":[],"elements":{"p1":{"kind":"Panel","spec":{"id":1,"title":"Up","vizConfig":{"kind":"VizConfig","group":"timeseries","spec":{}},"data":{"kind":"QueryGroup","spec":{"queries":[{"kind":"PanelQuery","spec":{"refId":"A","query":{"kind":"DataQuery","group":"prometheus","datasource":{"name":"<ds uid>"},"spec":{"expr":"up"}}}}]}}}}},"layout":{"kind":"GridLayout","spec":{"items":[{"kind":"GridLayoutItem","spec":{"x":0,"y":0,"width":24,"height":8,"element":{"kind":"ElementReference","name":"p1"}}}]}}}. For tabs, layout is {"kind":"TabsLayout","spec":{"tabs":[{"kind":"TabsLayoutTab","spec":{"title":"A","layout":<GridLayout>}}]}}.

Update non-secret datasource fields by UID in two steps. Called with only the uid, it returns the datasource's field schema and changes nothing. Called with the uid, schemaReviewed=true, and the changed values in the fields map, it applies the update. Omitted fields are preserved. Secrets (passwords, tokens) cannot be changed. Returns an update message and a health check.

Update an existing Grafana incident by ID. Allows changing the status ('active' or 'resolved'), the severity, the title, and custom field values. Only the provided fields are changed. Use this to resolve an incident, to correct its severity or title, or to fill in custom fields as part of an on-call workflow.

Get information about the current Grafana identity: login, email, name, whether it is a Grafana (server) admin, the current organization, and the organizations it can access (with roles). Call this to discover which orgId values are valid before targeting a specific organization, and to understand the identity's capabilities.

Validate a file in a provisioning repository at a given branch or commit by dry-run applying it. Returns whether the file would be accepted (valid), what resource action would result (create/update), the target resource type, and any structured validation errors. Use to confirm a draft dashboard or other resource will be accepted before merging or applying a PR — this is the same validation surface that Grafana's PR commenter reports.

概要

Grafana MCP Server (Official) とは？

Grafana MCP Server (Official) は Grafana Labs が公開しているオープンソースの Grafana MCP server（grafana/mcp-grafana）で、AI アシスタントが Grafana インスタンス上でダッシュボードを検索し、Prometheus や Loki などのデータソースをクエリし、アラート、インシデント、OnCall を管理できるようにします。

デフォルトでは stdio でローカル実行され（HTTP サービスとしても実行可能）、サービスアカウントトークンで Grafana に認証します。セルフマネージドの Grafana と Grafana Cloud の両方に対応し、すべての機能を使うには Grafana 9.0 以降が必要です。Grafana Cloud ユーザーは、後述する Grafana がホストする Cloud MCP Server を代わりに使うこともできます。

Grafana MCP Server (Official) の使い方

前提条件

  1. Grafana インスタンス（9.0 以降）または Grafana Cloud スタック。
  2. トークン付きの Grafana サービスアカウント。使用するツールに必要な RBAC 権限を付与してください。README では、組み込みの Editor ロールを割り当てるのがより簡単ですが、制限は緩くなると説明されています。
  3. 推奨の uvx インストールには uv が必要です。Docker や mcp-grafana バイナリも使えます。

環境変数を 2 つ設定します：GRAFANA_URL（例：http://localhost:3000、Grafana Cloud の場合は https://myinstance.grafana.net）と GRAFANA_SERVICE_ACCOUNT_TOKEN。旧来の GRAFANA_API_KEY は非推奨です。複数組織の環境では GRAFANA_ORG_ID で組織を指定します。

Claude Desktop

MCP クライアントの設定に次を追加します：

{
  "mcpServers": {
    "grafana": {
      "command": "uvx",
      "args": ["mcp-grafana"],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
      }
    }
  }
}

Docker を使う場合は、イメージのデフォルトのエントリポイントが SSE を実行するため、-t stdio で stdio モードに切り替える必要があります：

{
  "mcpServers": {
    "grafana": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "-e", "GRAFANA_URL", "-e", "GRAFANA_SERVICE_ACCOUNT_TOKEN", "grafana/mcp-grafana", "-t", "stdio"],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
      }
    }
  }
}

Cursor

Cursor では上と同じ mcpServers JSON を使います（README の Quick Start は Claude Desktop と Cursor を例に挙げています）。Cursor の MCP 設定に追加してください。

Claude Code

同じ uvx コマンドを Claude Code CLI で登録します：

claude mcp add grafana \
  -e GRAFANA_URL=http://localhost:3000 \
  -e GRAFANA_SERVICE_ACCOUNT_TOKEN=<your service account token> \
  -- uvx mcp-grafana

VS Code

サーバーを SSE サービスとして実行している場合（例：ポート 8000 で Docker イメージを実行）、README では次の .vscode/settings.json 設定が示されています：

"mcp": {
  "servers": {
    "grafana": {
      "type": "sse",
      "url": "http://localhost:8000/sse"
    }
  }
}

その他のインストール方法

README ではリリースバイナリ、go install github.com/grafana/mcp-grafana/v2/cmd/mcp-grafana@latest、Kubernetes 向けの Helm チャート（grafana/grafana-mcp）も紹介されています。SSE または streamable-http モードでは MCP_GRAFANA_SERVER_TOKEN を設定し、クライアントに bearer token の送信を必須にしてください。

Grafana MCP Server (Official) の主な機能

  • ダッシュボードの検索、取得、バージョン履歴、更新、パッチ。get_dashboard_summary や get_dashboard_property（JSONPath）などコンテキストを節約するツールも用意。
  • Prometheus と Loki に対する PromQL・LogQL クエリと、ラベル、メトリクス名、ログパターンなどのメタデータ探索。
  • Tempo のトレース検索と TraceQL メトリクス、Pyroscope のプロファイルクエリ。
  • アラートルール、サイレンス、通知ルーティングの管理と、Grafana Incident・Grafana OnCall のツール。
  • オプトインのカテゴリ：SQL データソース（ClickHouse、Snowflake、Athena、MySQL、PostgreSQL、MSSQL）、CloudWatch、Elasticsearch/OpenSearch、InfluxDB、Graphite、Quickwit、Google Cloud Logging、admin/RBAC。
  • ディープリンク生成と、パネルの PNG レンダリング（レンダリングには Grafana Image Renderer が必要）。
  • 安全制御：--disable-write（読み取り専用モード）、--disable-query、カテゴリごとの --disable-<category> フラグと --enabled-tools。
  • トランスポート：stdio（デフォルト）、SSE、streamable HTTP。TLS、呼び出し元認証、Prometheus メトリクス、OpenTelemetry トレーシングに対応。

Grafana MCP Server (Official) のツール

mcp.so のページには 79 個のツールが掲載されており、Grafana の領域ごとに分類できます：

  • ダッシュボードとフォルダ：search_dashboards、get_dashboard_by_uid、get_dashboard_summary、get_dashboard_panel_queries、update_dashboard、create_folder。大きなダッシュボードには summary または property ツールを使います。
  • データソースとクエリ：list_datasources、check_datasources_health、query_prometheus、query_prometheus_histogram、query_loki_logs、query_loki_patterns、search_tempo_traces、query_pyroscope。
  • アラート：alerting_rules_read、alerting_rules_write、alerting_silences_read、alerting_silences_write、alerting_manage_routing。
  • Incident と OnCall：create_incident、list_incidents、add_activity_to_incident、list_oncall_schedules、get_current_oncall_users、list_alert_groups。
  • アノテーション、スナップショット、レンダリング：create_annotation、get_annotations、create_snapshot、get_panel_image。
  • ナビゲーション、ドキュメント、汎用 API：generate_deeplink、search_docs、get_doc、user_info、そして専用ツールのない Grafana API エンドポイントを呼び出せる grafana_api_request。

一部のカテゴリ（admin、SQL、CloudWatch、Elasticsearch、runpanelquery、examples など）はデフォルトで無効になっており、--enabled-tools に追加する必要があります。

Grafana MCP Server (Official) のユースケース

  • インシデントのトリアージ：「今発火しているアラートルールはどれ？payments スケジュールの当番は誰？」
  • ログ調査：「checkout サービスの直近 1 時間のエラーログを Loki でクエリして、パターンを要約して。」
  • パネルを作らずにメトリクスを確認：「過去 24 時間の API の p95 リクエストレイテンシは？」
  • ダッシュボードの保守：「Kubernetes overview ダッシュボードを要約し、Pod 再起動数のパネルを追加して。」
  • メンテナンスウィンドウ：「env=staging のアラートに今日の 18 時までのサイレンスを作成して。」
  • コンテキストの共有：「そのパネルの直近 6 時間のディープリンクを生成して」、またはレポート用に PNG としてレンダリング。

Grafana MCP Server (Official) と代替ツールの比較

  • Grafana Cloud MCP Server（ホスト型）：Grafana は Grafana Cloud 専用のホスト型サーバーを https://mcp.grafana.com/mcp で提供しています。サービスアカウントトークンではなく OAuth のブラウザ認可を使い、スタックで Grafana Assistant が利用可能である必要があり、利用量は Assistant の課金に計上されます。オープンソースの mcp-grafana サーバーはセルフマネージドの Grafana にも対応し、ツールと権限を完全に制御できます。
  • コミュニティ製の Grafana MCP サーバー：非公式の Grafana サーバーも存在しますが、Grafana Labs がメンテナンスしているのは grafana/mcp-grafana です。
  • 関連するオブザーバビリティ系サーバー：メトリクスやログではなくエラートラッキングが目的なら、Sentry MCP Server を参照してください。

Grafana MCP Server (Official) のトラブルシューティング

  • get datasource by uid ... "id is invalid"（400）：Grafana が 9.0 より古く、/datasources/uid/{uid} エンドポイントがありません。9.0 以降にアップグレードしてください。
  • Claude Desktop で Error: spawn mcp-grafana ENOENT：command に mcp-grafana バイナリのフルパスを指定してください。
  • Docker コンテナが stdio でツールを使えない：-t stdio と -i を付けてください。イメージのデフォルトは SSE モードです。
  • 特定のツールで権限エラー：そのツールに必要な RBAC アクションやスコープ（例：データソース UID に対する datasources:query）がサービスアカウントにありません。権限を付与するか、Editor ロールを使ってください。
  • ダッシュボード操作でコンテキストウィンドウが埋まる：get_dashboard_by_uid より get_dashboard_summary と get_dashboard_property を優先し、不要なカテゴリを無効にしてください。--debug を付けると Grafana との HTTP 通信をログに出力できます。

よくある質問

1

Grafana MCP server は公式ですか？

はい。`github.com/grafana/mcp-grafana` は Grafana Labs が Apache-2.0 ライセンスで公開しており、Grafana のドキュメントでは OSS MCP Server と呼ばれています。

2

Grafana MCP server は無料ですか？

オープンソースのサーバーは無料で実行できます。Grafana のドキュメントによると、別途提供されるホスト型の Grafana Cloud MCP Server の利用量は Grafana Assistant の課金に計上されます。

3

Grafana MCP server にはどの認証情報が必要ですか？

Grafana の URL（`GRAFANA_URL`）とサービスアカウントトークン（`GRAFANA_SERVICE_ACCOUNT_TOKEN`）です。ユーザー名とパスワード（`GRAFANA_USERNAME`、`GRAFANA_PASSWORD`）にも対応しています。`GRAFANA_API_KEY` は非推奨です。

4

Grafana Cloud で使えますか？

はい。`GRAFANA_URL` に `https://myinstance.grafana.net` のようなスタックの URL を設定します。Grafana Cloud ユーザーはホスト型サーバー `https://mcp.grafana.com/mcp` も利用できます。

5

Grafana MCP server は Claude Code、Cursor、VS Code で使えますか？

はい。標準的な stdio MCP サーバーなので、どの MCP クライアントからも `uvx mcp-grafana` を起動できます。VS Code からは SSE や streamable HTTP で接続することもできます。

6

Grafana MCP server を読み取り専用モードで実行できますか？

はい。`--disable-write` を付けて起動すると、作成・更新・削除のツールが削除されます。`--enable-query` を渡さない限り、生 SQL のクエリツールも削除されます。`--disable-query` はすべてのデータソースクエリツールを削除します。

7

必要な Grafana のバージョンは？

Grafana 9.0 以降です。それより古いバージョンでは一部のデータソース操作が失敗します。

8

リモートサーバーですか、ローカルサーバーですか？

デフォルトでは stdio でローカル実行されますが、Docker、バイナリ、Helm を使って SSE または streamable-HTTP サービスとして実行することもできます。ネットワークに公開する場合は `MCP_GRAFANA_SERVER_TOKEN` を設定してください。

コメント

「開発者ツール」の他のコンテンツ

Capgo MCP

Cap-go

Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

Windframe

Windframe MCP gives your AI the design taste needed to create consistent, production-ready UI that feels intentionally designed. Available at https://windframe.dev/mcp

Vibgrate MCP

Vibgrate

Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

3

Pugi

Pugi Inc.

Pugi is an AI product team that builds, checks and publishes websites and apps. Its MCP server gives agents a passive website security check graded A+ to F (headers, TLS, cookies, exposed keys in scripts), free with a no

Yocoolab

Yocoolab

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

1
広告掲載