grafana-mcp
This server provides comprehensive access to manage and query a Grafana instance through the MCP protocol, covering dashboards, datasources, alerting, and more.
Dashboard Management: Search by title/tag/folder, get by UID, create/update with full JSON model support, delete, and list all folders.
Datasource Operations: List all configured datasources, get a specific datasource by name or ID, and run instant or range queries against any datasource.
InfluxDB Exploration: List databases, measurements, field keys, tag keys, tag values, and retention policies for InfluxDB datasources.
Alerting Management: List, get, create, update, and delete Grafana-managed alert rules; retrieve the notification policy tree and list contact points.
Health Check: Verify the Grafana instance status and version.
Provides tools to interact with a Grafana instance, including searching, fetching, creating, updating, and deleting dashboards; managing datasources; running queries; managing alert rules, notification policies, and contact points; listing folders; and checking health.
Provides tools to query InfluxDB databases through a Grafana datasource, including listing databases, measurements, field keys, tag keys, tag values, and retention policies.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@grafana-mcpsearch for dashboards related to CPU usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Grafana-MCP
An MCP (Model Context Protocol) server that gives Bob direct access to your Grafana instance — dashboards, datasources, queries, alerting rules, and more.
Prerequisites
Node.js v18 or later
A running Grafana instance
A Grafana user with sufficient permissions (Admin recommended for full access)
Related MCP server: Grafana MCP Server
Installation
Install dependencies and build
git clone <url>
cd grafana-mcp
npm install
npm run buildThe compiled server is now at build/index.js.
Configuration
The server reads three required environment variables and one optional one:
Variable | Description |
| Base URL of your Grafana instance, e.g. |
| Grafana username |
| Grafana password |
| Optional: SOCKS5 proxy URL, e.g. |
Registering with Bob
There are two places you can register the server. Most users will prefer the global config so the server is available in every Bob workspace without any per-project setup.
Option A — Global config (recommended)
Edit ~/.bob/settings/mcp.json (Windows: %USERPROFILE%\.bob\settings\mcp.json) and add the server entry. Replace the path with the absolute path to the built entry point on your machine:
{
"mcpServers": {
"grafana-mcp": {
"command": "node",
"args": ["C:\\absolute\\path\\to\\grafana-mcp\\build\\index.js"],
"env": {
"GRAFANA_URL": "http://your-grafana-host:3000",
"GRAFANA_USER": "admin",
"GRAFANA_PASSWORD": "your-password",
"SOCKS_PROXY": "socks5://<proxy-host>:<port>"
}
}
}
}
SOCKS_PROXYis optional — omit it if you don't need a proxy.
Option B — Project/workspace config
Add the same entry to .bob/mcp.json at the root of a specific workspace. This scopes the server to that project only.
{
"mcpServers": {
"grafana-mcp": {
"command": "node",
"args": ["/absolute/path/to/grafana-mcp/build/index.js"],
"env": {
"GRAFANA_URL": "http://your-grafana-host:3000",
"GRAFANA_USER": "admin",
"GRAFANA_PASSWORD": "your-password",
"SOCKS_PROXY": "socks5://<proxy-host>:<port>"
}
}
}
}
SOCKS_PROXYis optional — omit it if you don't need a proxy.
To point at a different Grafana instance, change GRAFANA_URL (and credentials as needed) in whichever config file you used.
Available Tools
Tool | Description |
| Search dashboards by title, tag, or folder |
| Fetch a dashboard by UID |
| Create or update a dashboard |
| Delete a dashboard by UID |
| List all configured datasources |
| Get a datasource by name or ID |
| Run instant/range queries via Grafana's |
| List InfluxDB databases through a Grafana datasource |
| List measurements in an InfluxDB database |
| List numeric field keys for a measurement |
| List indexed tag keys for a measurement |
| Enumerate values for a specific tag key |
| List retention policies for an InfluxDB database |
| List Grafana-managed alerting rules |
| Get an alert rule by UID |
| Create a new alert rule via the provisioning API |
| Update an existing alert rule |
| Delete an alert rule by UID |
| Get the alert notification policy tree |
| List all notification contact points |
| List all dashboard folders |
| Check the health and version of the Grafana instance |
Troubleshooting
If MCP server shows "disconnected" in Bob IDE
The system node binary requires a version of c-ares that might not be installed on the machine. Try using the node binary bundled with Bob IDE instead — it has everything it needs built in.
Find it:
find ~/.bobide-server/bin -name "node" -type fThen update command in your MCP config:
"command": "/root/.bobide-server/bin/<hash>/node"Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jason-Shi-1/grafana-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server