Does every team member need their own GitHub account?

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

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

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

GitHub · Claude

GitHub in Claude. In five minutes.

Connect GitHub 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 GitHub in Loopthink
Fine-grained personal access token, read permissions, selected repositories.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which pull requests have waited for a review for more than three days?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Resource owner: your organisation. Repository access: only the repositories your team should reach.
2
Permissions: Contents Read, Issues Read, Pull requests Read, Actions Read. Metadata is included. Nothing on Write. An organisation owner approves the token once.
3
Paste the token into Loopthink. Your team never sees it; each person signs in with their own identity.
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: GitHub MCP server · Set up the GitHub MCP server · Fine-grained personal access tokens · Token permissions · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Use cases

What people actually ask Claude about GitHub.

Engineering
“Which pull requests have waited for a review for more than three days?”
Product
“Which issues labelled customer-bug were closed this sprint, and which are still open?”
Management
“How many releases shipped this quarter, and did any deploy workflow fail?”

Why Loopthink

GitHub has an MCP server. Why Loopthink?

GitHub's official MCP server signs in one person with OAuth and ships write tools for issues, pull requests, files and merges unless you remember the read-only switch.

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

Tool	Engineering	Product	Management
Repositories & code	Engineering may use Repositories & code	Product may not use Repositories & code	Management may not use Repositories & code
Issues	Engineering may use Issues	Product may use Issues	Management may use Issues
Pull requests	Engineering may use Pull requests	Product may use Pull requests	Management may use Pull requests
Actions runs	Engineering may use Actions runs	Product may not use Actions runs	Management may use Actions runs
Security alerts	Engineering may use Security alerts	Product may not use Security alerts	Management may not use Security alerts
Write actions off by default	Engineering may not use Write actions	Product may not use Write actions	Management may not use Write actions

Masked for every role: commit author emails, secrets and tokens quoted in issues, external contributors' names.

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

GitHub 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