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 the model see?

The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to Claude. The model gets the numbers, not the people.

Is there an audit trail?

Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.

Free for one person and two MCP servers, forever, no card. Starter is €39 per month and adds roles, an identity of their own for every colleague, field masking and a 30-day audit. Team is €99 and adds your own APIs and SQL databases, your own domain and your own identity provider. Prices are on the pricing page, 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

Connect Grafana to Claude. For your whole team.

The official Grafana MCP runs with one service account token, org-wide, and its README recommends the Editor role. Loopthink holds a Viewer token, gives every Claude user in your team their own login, and lets SRE, Developers and Management query the dashboards, alerts and logs their role allows.

Start free Get a demo

Free for 2 servers, no card · Paid plans from €39 · EU-hosted

The problem

Grafana in a chat client, today.

Today a team that wants Grafana in an AI client creates one service account token and passes it around. Even a Viewer token can query every data source in the organisation, so a chat can pull production logs with IP addresses in them. If the token was Editor, as the official server suggests, a chat can also silence alerts, and Grafana logs the service account, not the person.

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

Who may do what

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 MCP servers for one person, no card. The roles, the identity per person and the masking above start at €39 a month, as soon as colleagues join. See the plans

What you get

Four checks between Claude and Grafana.

01
Identify
OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.
02
Authorize
Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.
03
Mask
Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.
04
Log
Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.

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?”

Each question runs as the person who asked it, with that person's role. A Developers colleague asking the SRE question gets the tools their own role allows, not an error, not more.

Compare

Four ways to put Grafana into Claude.

	Native Grafana connector	Build it yourself	Enterprise gateways¹	Loopthink
Per-user identity	One personal login, all its rights	Only if you build it	Yes	Yes, every call runs as the person who asked
Tool-level roles	No	Your code	Yes	Yes, write off by default
Field masking	No	Your code	Not documented	Yes, before the model sees the data
Published price	Included in your Grafana plan	Your engineers' time	Contact sales	Free, paid from €39
EU company	No	Whatever you are	Mostly US	Yes, Germany

Native Grafana connector: Official Grafana MCP server with one service account token. Org-wide Viewer or Editor, shared by everyone who copies the config.

¹ MintMCP, MCP Manager, Pomerium

Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative

Also for

ChatGPT

Connect another system to Claude

All systems and clients →

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 the model see?: The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to Claude. The model gets the numbers, not the people.
Is there an audit trail?: Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.
What does it cost?: Free for one person and two MCP servers, forever, no card. Starter is €39 per month and adds roles, an identity of their own for every colleague, field masking and a 30-day audit. Team is €99 and adds your own APIs and SQL databases, your own domain and your own identity provider. Prices are on the pricing page, 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 in Claude, with rules.

One key in Loopthink, one login per person, one matrix that decides who may do what.