When to use Grafana Assistant vs MCP vs GCX: Grafana Assistant
Grafana has three AI things people keep confusing — Assistant, MCP, and GCX. They’re not competitors. Think of it as a brain and two hands. In this short, I start with the brain: Grafana Assistant.
Assistant isn’t just a chatbot — it’s the reasoning layer. It manages context and knows your Grafana: your dashboards, your data sources, a knowledge graph of your infrastructure. Instead of clicking around, you tell Assistant what you want to do and it figures out the how.
Reach for the Assistant when the work is visual or exploratory:
- Building a dashboard? Assistant.
- “Teach me how to do this” or “where is this in the UI”? Assistant.
- A real incident that needs root-cause analysis across multiple data sources? Assistant. That’s its sweet spot — it forms a hypothesis, correlates your signals, and can even open a pull request with the fix.
Here’s the key thing though: Assistant is Grafana’s own brain — but it’s not the only brain that can drive Grafana. That’s where the two hands come in, and I’ll cover the first of those (the MCP server) next.
Transcript
Grafana has three AI things people keep confusing — Assistant, MCP, and GCX. I’m going to talk a bit about each one so you know which one is best for your use case.
Spoiler: They’re not competitors. Think of it as a brain and two hands.
Let’s start with Grafana Assistant, which is the brain.
It’s not just a chatbot — it’s the reasoning layer. It manages context, it knows your Grafana: your dashboards, your data sources, a knowledge graph of your infrastructure. So instead of you clicking around to do something, you can say what you want to do to Assistant and it figures out the how.
Reach for the Assistant when the work is visual or exploratory.
- If you’re building a dashboard? Assistant.
- “Teach me how to do this” or “where is this in the UI”? Assistant.
- You have a real incident where you need root-cause analysis across multiple data sources? Assistant.
- That’s its sweet spot — it forms a hypothesis, correlates your signals, and can even open a pull request with the fix.
Here’s the key thing though: Assistant is Grafana’s own brain — but it’s not the only brain that can drive Grafana. That’s where the two hands come in… and I’ll show you those next.
Resources
- Grafana Assistant (product page)
- My notes on Grafana Assistant
- My notes on GCX
- Unlearnings from building Grafana Assistant — my Context Horizon piece