Does every team member need their own PostHog account?

No. Loopthink holds one key or token for PostHog. Your people sign in to Loopthink with their own identity, and every call to PostHog is logged under their name. Seats in PostHog 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 PostHog key live?

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

Can somebody write to PostHog 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 PostHog. 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.

PostHog · Claude

PostHog in Claude. In five minutes.

Connect PostHog 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 PostHog in Loopthink
Personal API key, read scopes, one project.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which feature flags are rolled out to more than half of users right now?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
PostHog → Settings → Personal API keys → Create personal API key. Skip the MCP Server preset; it grants write scopes.
2
Hand-pick read scopes: insight:read, query:read, feature_flag:read, error_tracking:read, session_recording:read, project:read. Organisation and project access: the one project your team uses.
3
Copy the key once and paste it into Loopthink. It stays on our side; the team only ever sees tools.
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: PostHog MCP server · MCP tools · Personal API keys · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Use cases

What people actually ask Claude about PostHog.

Product
“Which feature flags are rolled out to more than half of users right now?”
Engineering
“How many errors of type TypeError since yesterday's release, and on which page?”
Management
“Weekly active users this month versus last month?”

Why Loopthink

PostHog has an MCP server. Why Loopthink?

The official PostHog MCP runs on a personal API key, and the key preset its docs point to grants write access on nearly everything: feature flags, persons, recordings.

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 PostHog account?: No. Loopthink holds one key or token for PostHog. Your people sign in to Loopthink with their own identity, and every call to PostHog is logged under their name. Seats in PostHog 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 PostHog key live?: In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in PostHog whenever you like and paste the new one once.
Can somebody write to PostHog 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 PostHog. 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 PostHog. Roles across, tools down.

Tool	Product	Engineering	Management
Insights & trends	Product may use Insights & trends	Engineering may use Insights & trends	Management may use Insights & trends
Events & persons	Product may use Events & persons	Engineering may not use Events & persons	Management may not use Events & persons
Feature flags	Product may use Feature flags	Engineering may use Feature flags	Management may not use Feature flags
Session recordings	Product may use Session recordings	Engineering may not use Session recordings	Management may not use Session recordings
Error tracking	Product may use Error tracking	Engineering may use Error tracking	Management may not use Error tracking
Write actions off by default	Product may not use Write actions	Engineering may not use Write actions	Management may not use Write actions

Masked for every role: person emails and distinct IDs, IP addresses, session recording links.

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

PostHog 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