Does every team member need their own Grafana account?

No. Loopthink holds one key or token for Grafana. Your people sign in to Loopthink with their own identity, and every call to Grafana is logged under their name. Seats in Grafana stay where they are today.

Who has to add the connector in Claude?

One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.

Where does the Grafana key live?

In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in Grafana whenever you like and paste the new one once.

Can somebody write to Grafana from the chat?

Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.

Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.

We already run our own MCP server for Grafana. Does it still work?

Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

Grafana · Claude

Grafana in Claude. In five minutes.

Connect Grafana in Loopthink, paste one URL into Claude, ask. Hosted in the EU, every call logged.

Start free See the steps

Free for 2 connectors, no card · Pro €19 · EU-hosted

How to connect

Three steps. The third one is asking.

1
Connect Grafana in Loopthink
Service account token, Viewer role.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which alerts fired in the last 24 hours, and are any of them still firing?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
Grafana → Administration → Users and access → Service accounts → Add service account. Role: Viewer.
2
Open the account → Add service account token. Set an expiration date; Loopthink tells you before it runs out.
3
Paste the token and your Grafana URL into Loopthink. Nobody on the team handles it again.
4
Open Settings, then Connectors, then Add, and choose Add custom connector. The dialog asks for exactly two things: a name your colleagues will recognise, and the MCP server URL, which is your Loopthink connector URL.
5
Continue, and Claude reads the server before it asks you anything. It detects that the server signs people in, and that it can register itself, so the sign-in and OAuth-client options are already chosen. Nothing has to be typed there, no client id, no secret, no request header.
6
Add it, then each team member opens Connectors, clicks Connect on it and signs in once with their own account. In a chat the connector appears in the + menu. Toggle it on and ask.

Steps checked against the vendor documentation on 17 September 2026: Service accounts · Data source permissions · Grafana MCP server · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Use cases

What people actually ask Claude about Grafana.

SRE
“Which alerts fired in the last 24 hours, and are any of them still firing?”
Developers
“Show me the p95 latency of checkout-api over the last seven days.”
Management
“Uptime of the customer portal this month, against the 99.9 target?”

Why Loopthink

Grafana has an MCP server. Why Loopthink?

The official Grafana MCP runs with one service account token, org-wide, and its README recommends the Editor role.

Loopthink runs hosted and gives Claude a URL. Every colleague signs in with their own account and sees only what you ticked.

FAQ

Before you connect.

Does every team member need their own Grafana account?: No. Loopthink holds one key or token for Grafana. Your people sign in to Loopthink with their own identity, and every call to Grafana is logged under their name. Seats in Grafana stay where they are today.
Who has to add the connector in Claude?: One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
Where does the Grafana key live?: In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in Grafana whenever you like and paste the new one once.
Can somebody write to Grafana from the chat?: Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
What does it cost?: Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.
We already run our own MCP server for Grafana. Does it still work?: Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

When colleagues join

One matrix for Grafana. Roles across, tools down.

Tool	SRE	Developers	Management
Dashboards	SRE may use Dashboards	Developers may use Dashboards	Management may use Dashboards
Data source queries	SRE may use Data source queries	Developers may use Data source queries	Management may not use Data source queries
Alerts & incidents	SRE may use Alerts & incidents	Developers may use Alerts & incidents	Management may use Alerts & incidents
Logs (Loki)	SRE may use Logs (Loki)	Developers may use Logs (Loki)	Management may not use Logs (Loki)
OnCall schedule	SRE may use OnCall schedule	Developers may not use OnCall schedule	Management may not use OnCall schedule
Write actions off by default	SRE may not use Write actions	Developers may not use Write actions	Management may not use Write actions

Masked for every role: IP addresses in log lines, user emails in annotations, contact point addresses.

You set this once. Every Claude user in your team gets exactly this.

Grafana runs on the free tier: two connectors for one person, no card. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans