diff --git a/content/guides/grafana-mcp-server-gemini.md b/content/guides/grafana-mcp-server-gemini.md
new file mode 100644
index 000000000000..9f2443194ea3
--- /dev/null
+++ b/content/guides/grafana-mcp-server-gemini.md
@@ -0,0 +1,157 @@
+---
+description: Integrate Gemini CLI with Grafana via Docker MCP Toolkit for natural language observability.
+keywords: mcp, grafana, docker, gemini, devops
+title: Connect Gemini to Grafana via MCP
+summary: |
+  Learn how to leverage the Model Context Protocol (MCP) to interact with Grafana dashboards and datasources directly from your terminal.
+levels: [intermediate]
+subjects: [devops]
+aliases:
+  - /guides/use-case/devops/
+params:
+  time: 15 minutes
+---
+
+# Integrating Gemini CLI with Grafana via Docker MCP Toolkit
+
+This guide outlines the process of connecting Gemini CLI to a Grafana instance using the **Docker MCP Toolkit**. By leveraging the Model Context Protocol (MCP), we enable natural language querying of observability data directly from the terminal.
+
+## Prerequisites
+
+* **Gemini CLI** installed and authenticated.
+* **Docker Desktop** with the **MCP Toolkit** extension enabled.
+* An active **Grafana** instance.
+
+
+## 1. Provisioning Grafana Access
+
+The MCP server requires a **Service Account Token** to interact with the Grafana API. Using a personal API key is discouraged for security best practices.
+
+1. Navigate to **Administration > Users and access > Service accounts** in your Grafana dashboard.
+2. Create a new Service Account (e.g., `gemini-mcp-connector`).
+3. Assign the **Viewer** role (or **Editor** if you require alert management capabilities).
+4. Generate a new token. **Copy the token value immediately**; it will not be displayed again.
+
+![Create a service account in Grafana](images/create-sa-grafana.webp)
+
+
+
+## 2. MCP Server Configuration
+
+The Docker MCP Toolkit provides a pre-configured Grafana catalog item. This acts as the bridge between the LLM and the Grafana API.
+
+1. Open the **MCP Toolkit** in Docker Desktop.
+2. Locate **Grafana** in the Catalog and add it to your active servers.
+3. In the **Configuration** view, define the following:
+* **Grafana URL:** The endpoint or URL of your instance.
+* **Service Account Token:** The token generated in the previous step.
+
+![Configure mcp grafana in docker](images/configure-mcp-grafana.webp)
+
+
+
+## 3. Gemini CLI Integration
+
+To register the Docker MCP gateway within Gemini, update your global configuration file located at `~/.gemini/settings.json`.
+
+Ensure the `mcpServers` object includes the following entry:
+
+```json
+{
+  "mcpServers": {
+    "MCP_DOCKER": {
+      "command": "docker",
+      "args": [
+        "mcp",
+        "gateway",
+        "run"
+      ]
+    }
+  }
+}
+
+```
+
+
+## 4. Operational Validation
+
+Restart your Gemini CLI session to load the new configuration. Verify the status of the MCP tools by running:
+
+```bash
+> /mcp list
+
+```
+
+![MCP Docker added to gemini cli](images/mcp-docker-gemini.webp)
+
+A successful connection will show `MCP_DOCKER` as **Ready**, exposing over 61 tools for data fetching, dashboard searching, and alert inspection.
+
+## Use Cases
+
+### Datasource Discovery
+
+_List all Prometheus and Loki datasources._
+
+![List datasources](images/gemini-grafana-list-datasources.webp)
+
+
+
+![List datasources](images/list-datasources-result.webp)
+
+
+### Logs Inspection
+
+The sequence initiates with the User Prompt: "I would like to filter logs based on the device_name=edge-device-01 label. Are there logs about nginx in the last 5 minutes?". At this stage, the Gemini model performs intent parsing. It identifies the specific metadata required—a label (device_name) and a keyword (nginx)—and realizes it needs external data to fulfill the request. This triggers the list_datasources tool through the MCP Server to locate the telemetry backend.
+
+![Filter logs based on loki labels](images/mcp-docker-grafana-loki-1.webp)
+
+Once the system identifies Loki as the active datasource, it translates the human intent into a precise technical command. The AI autonomously constructs a LogQL `query: {device_name="edge-device-01"} |= "nginx"`. This query targets the specific Kubernetes pod logs, extracting raw OpenTelemetry (OTel) data that includes pod UIDs and container metadata. Instead of the user writing complex syntax, the prompt acts as the bridge to pull structured data from the containerized environment
+
+
+![Gemini gets the Grafana's logs from MCP docker](images/mcp-docker-grafana-loki-2.webp)
+
+In the final step, Gemini performs reasoning over the raw data. It filters through hundreds of lines of telemetry to confirm that Nginx logs exist, but it goes beyond the original prompt by identifying a critical anomaly. It flags a `node_filesystem_device_error`, alerting the DevOps engineer to a potential hardware or volume mounting issue on the edge node. The process concludes by turning a simple question into an actionable incident report.
+
+![Gemini gives an overall about the findings](images/mcp-docker-grafana-loki-3.webp)
+
+
+
+### Dashboard Navigation 
+
+_How many dashboards we have?_
+
+![List datasources](images/mcp-grafana-dashboards.webp)
+
+
+_Tell me the summary of X dashboard_
+
+
+![List datasources](images/mcp-grafana-summary-dashboard.webp)
+
+### Other scenarios
+
+Imagine you get a page that an application is slow. You could:
+
+   1. Use list_alert_rules to see which alert is firing.
+   2. Use search_dashboards to find the relevant application dashboard.
+   3. Use get_panel_image on a key panel to see the performance spike visually.
+   4. Use query_loki_logs to search for "error" or "timeout" messages during the time of the spike.
+   5. If you find the root cause, use create_incident to start the formal response and add_activity_to_incident to log your findings.
+
+## Next steps?
+
+This use case demonstrates the future of Operational Intelligence: moving away from manual dashboard hunting and complex query syntax toward a conversational, proactive troubleshooting experience.
+
+By bridging the gap between your terminal and Grafana's telemetry via the Docker MCP Toolkit, you empower your DevOps team to detect silent failures—like the filesystem error identified in our example—before they escalate into full-scale outages.
+
+Don't let critical logs get buried under layers of infrastructure noise. Start automating your incident response and log analysis today.
+
+Take the next step:
+
+- Deploy the connector: Follow the 15-minute guide above to link your local Gemini CLI to your production Grafana instance.
+
+- Scale the solution: Explore how to share these MCP configurations across your SRE team for unified troubleshooting.
+
+- Optimize your queries: Experiment with advanced LogQL prompts to create automated health reports.
+
+Need help setting up your Docker MCP environment or customizing your Gemini prompts? Let's know.
diff --git a/content/guides/images/configure-mcp-grafana.webp b/content/guides/images/configure-mcp-grafana.webp
new file mode 100644
index 000000000000..f1e8f3624552
Binary files /dev/null and b/content/guides/images/configure-mcp-grafana.webp differ
diff --git a/content/guides/images/create-sa-grafana.webp b/content/guides/images/create-sa-grafana.webp
new file mode 100644
index 000000000000..8b8bae9b98cf
Binary files /dev/null and b/content/guides/images/create-sa-grafana.webp differ
diff --git a/content/guides/images/gemini-grafana-list-datasources.webp b/content/guides/images/gemini-grafana-list-datasources.webp
new file mode 100644
index 000000000000..c87aed0d8af0
Binary files /dev/null and b/content/guides/images/gemini-grafana-list-datasources.webp differ
diff --git a/content/guides/images/list-datasources-result.webp b/content/guides/images/list-datasources-result.webp
new file mode 100644
index 000000000000..965301351c1f
Binary files /dev/null and b/content/guides/images/list-datasources-result.webp differ
diff --git a/content/guides/images/mcp-docker-gemini.webp b/content/guides/images/mcp-docker-gemini.webp
new file mode 100644
index 000000000000..623fe258d7c1
Binary files /dev/null and b/content/guides/images/mcp-docker-gemini.webp differ
diff --git a/content/guides/images/mcp-docker-grafana-loki-1.webp b/content/guides/images/mcp-docker-grafana-loki-1.webp
new file mode 100644
index 000000000000..db4c3c30097a
Binary files /dev/null and b/content/guides/images/mcp-docker-grafana-loki-1.webp differ
diff --git a/content/guides/images/mcp-docker-grafana-loki-2.webp b/content/guides/images/mcp-docker-grafana-loki-2.webp
new file mode 100644
index 000000000000..ddc7cc4005c9
Binary files /dev/null and b/content/guides/images/mcp-docker-grafana-loki-2.webp differ
diff --git a/content/guides/images/mcp-docker-grafana-loki-3.webp b/content/guides/images/mcp-docker-grafana-loki-3.webp
new file mode 100644
index 000000000000..55172ee86dc9
Binary files /dev/null and b/content/guides/images/mcp-docker-grafana-loki-3.webp differ
diff --git a/content/guides/images/mcp-grafana-dashboards.webp b/content/guides/images/mcp-grafana-dashboards.webp
new file mode 100644
index 000000000000..90e570957cb4
Binary files /dev/null and b/content/guides/images/mcp-grafana-dashboards.webp differ
diff --git a/content/guides/images/mcp-grafana-summary-dashboard.webp b/content/guides/images/mcp-grafana-summary-dashboard.webp
new file mode 100644
index 000000000000..d616267076fb
Binary files /dev/null and b/content/guides/images/mcp-grafana-summary-dashboard.webp differ