Grafana MCP for AI Agents. Command your entire observability stack via conversation.
Grafana MCP lets your AI agent search, inspect, and manage all system monitoring data directly through natural conversation. You can find specific dashboards by tag or title, pull exact PromQL/LogQL queries from panels, audit connected data sources (Prometheus, Loki), and check the status of firing alerts—all without logging into the Grafana UI.
Give Claude and any AI agent real-world access
Find the unique IDs and basic info for monitoring dashboards without browsing the Grafana UI.
Retrieve a dashboard's entire setup, including every panel's specific query string (PromQL, LogQL, or SQL).
Audit all the types of databases and services—like Loki, Prometheus, or CloudWatch—that your Grafana instance uses.
View a list of alert rules that are currently in 'firing' state to understand immediate system health issues.
Ask an AI about this
Waiting for input…
What AI agents can do with Grafana: 4 Tools for Observability
Use these tools to search dashboards by tag, retrieve panel configurations, list connected data sources, or monitor active system alerts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Grafana MCPSearch Dashboards
Searches Grafana for dashboards by a title or tag, returning their basic metadata and unique ID.
Get Dashboard
Retrieves the complete configuration of a specific dashboard, including all panel...
List Datasources
Lists every configured data source available in your Grafana instance for auditing...
Firing Alerts
Retrieves a list of all alert rules that are currently active and reporting an issue.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Grafana, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Grafana. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The struggle of navigating complex dashboards Solved with Vinkius AI Gateway
Today, checking system health means logging into Grafana. You click 'Metrics,' then you check a tab for alerts. If an alert is firing, you have to manually find the associated dashboard ID and open it up just to see what queries are running. Copying those complex PromQL strings—the ones that actually tell you *why* something failed—is tedious clicking and copy-pasting across five different tabs.
With this MCP, you skip all that UI navigation. You just ask your agent: 'What's wrong with the API service?' It handles finding the right dashboard, retrieving the necessary query strings via `get_dashboard`, and providing you with actionable data immediately in plain text.
Grafana MCP Gives You Complete Observability Control
The manual steps that disappear are: 1) Finding the right dashboard ID; 2) Navigating to the panel settings; 3) Copying complex, multi-line queries. These actions used to take multiple clicks and required context switching.
Now, you manage your entire observability stack—from checking `firing_alerts` status to pulling raw data source metadata using `list_datasources`—all from a single chat window. It's that simple.
What your AI can actually do with this
Monitoring complex systems used to mean clicking through tabs and manually copying IDs. Now, you can connect your observability stack directly to your agent. This MCP gives you full control over dashboard inspections and alerting workflows using only conversation. You tell your AI client what's wrong—maybe latency spiked or an alert fired—and it handles the deep dive.
It searches for relevant dashboards by title or tag right in the chat window, pulling back metadata instantly. Need to know why the metric failed? The agent can retrieve the full configuration of any dashboard, giving you precise PromQL, LogQL, or SQL queries and panel layouts. Plus, it lists every data source connected—whether that's Prometheus or CloudWatch—so you always know where your metrics are coming from.
When you connect this MCP via Vinkius, your agent doesn't just read dashboards; it becomes a full SRE command center right in your chat interface.
019d75aa-7428-7281-bf68-5d4097fc9cae Here's how it actually works
The bottom line is you manage complex observability data conversationally, bypassing multiple manual UI steps.
Subscribe to this MCP on Vinkius.
Enter your Grafana Instance URL and the Service Account Token into your AI client.
Ask your agent anything—like 'Show me all dashboards tagged 'production'' or 'What is the query for dashboard abc-123?'
Who is this actually for?
Anyone whose job involves troubleshooting live system issues or understanding complex metric pipelines. This is for the ops engineer who's tired of clicking through dozens of dashboards at 2 a.m., and the cloud architect who needs to verify data source boundaries quickly.
Uses this MCP to check active alert rules or pull specific dashboard queries instantly during an incident, eliminating manual navigation.
Connects this MCP to validate metrics and logs by extracting the underlying PromQL or LogQL queries from existing dashboards for debugging purposes.
Audits data source configurations across different services (e.g., verifying connectivity between SQL databases and Grafana) using simple natural language requests.
What Changes When You Connect
Find relevant monitoring data instantly. Use search_dashboards to locate dashboards by tag or title, getting the unique ID needed for deeper inspection without manual searching.
Extract raw queries on demand. The get_dashboard tool pulls the full configuration of any panel, giving you exact PromQL, LogQL, or SQL query strings immediately.
Audit infrastructure connectivity easily. Use list_datasources to get a definitive list of every database (like Prometheus or CloudWatch) connected to your Grafana instance for security checks.
Know what's broken right now. The firing_alerts tool checks current alert rules and tells you exactly which services are experiencing active issues.
Reduce troubleshooting time dramatically. Instead of opening the UI, running multiple searches, and copy-pasting IDs, your agent does it all in one chat session.
See it in action
Investigating a recent spike in request latency
A developer sees high latency metrics. They ask their agent to check for active alerts using firing_alerts. The agent finds an alert on the API service, which points them toward Dashboard ABC-123. They then use get_dashboard to pull the exact PromQL query for that panel and share it with the backend team.
Onboarding a new cloud architect
A new architect needs to understand all data inputs. Instead of reading documentation, they ask their agent to use list_datasources. The agent responds with a clear list of every connected source—Prometheus, SQL, and more—allowing the architect to map out the entire data landscape.
Debugging performance regressions
The team notices dashboard metrics are suddenly wrong. They use search_dashboards first to confirm the correct ID for the affected view. Then, they pass that UID to get_dashboard and pull all underlying queries, quickly identifying if a query syntax changed.
Preparing for a major deployment
Before launch, the DevOps team needs to verify which dashboards exist in the staging environment. They ask their agent to search by 'staging' tag using search_dashboards, getting a manifest of all monitoring views that need testing.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Copying queries manually
A user has to open the Grafana UI, navigate deep into dashboard settings, and copy complex PromQL strings character by character. This takes minutes of clicking.
Use your agent with get_dashboard. Give it the UID you found via search_dashboards, and it pulls the full query string instantly for you.
Guessing dashboard UIDs
A user remembers a dashboard is about 'database performance' but doesn't know its unique ID, leading to multiple failed attempts or wrong dashboards.
Start by running search_dashboards with tags like 'production' or 'database'. This gives you the exact UID needed for all subsequent inspections.
Ignoring data source boundaries
A developer assumes a metric is coming from Prometheus, but later discovers it's actually sourced from CloudWatch Logs because they never checked connectivity.
Always run list_datasources first. This provides an audit of every connected system so you know exactly where the data originates.
When It Fits, When It Doesn't
Use this MCP if your primary need is deep, conversational inspection of existing monitoring dashboards and alert states within Grafana. You want to retrieve queries (get_dashboard), check alerts (firing_alerts), or audit connections (list_datasources). Don't use it if you need to build new dashboards from scratch, manage user permissions, or interact with infrastructure code (like Terraform). For those cases, you need a separate configuration management tool. This MCP is for read-only observability data deep dives; it doesn't write back to the Grafana instance.
Questions you might have
How does the Grafana MCP handle different query languages? +
It handles PromQL, LogQL, and SQL queries. When you use get_dashboard, the agent extracts the exact language used for each specific panel's data source.
Can I check alert status with Grafana MCP if I don't know the service name? +
Yes, the MCP checks active alerts using firing_alerts and reports on all currently firing rules. You don't need to specify a service; it just lists what's going off.
Does Grafana MCP let me edit dashboards? +
No, this MCP is for reading and inspecting data only. It provides the details needed (like queries or UIDs) but cannot modify any settings in your Grafana instance.
What if I need to find a dashboard that uses an old data source? +
Run list_datasources first. This shows all configured sources, helping you identify the right connection type before searching for dashboards using that data.
Powerful workflows you can unlock today
MCP Recipe for Full-Stack Observability
Two monitoring tools, zero correlation , your Datadog alerts say 'high latency' and your Grafana dashboards say 'database connections maxed' but nobody connected the dots until the postmortem
MCP Servers for Global Edge Performance
Cache hit ratios monitored, edge latency tracked, WAF threats counted, performance reports delivered , run your edge infrastructure from one prompt