Does every team member need their own Any REST API account?

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

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

Can somebody write to Any REST API 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 Any REST API. 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.

Any REST API · Claude

Any REST API in Claude. In five minutes.

Connect Any REST API 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 Any REST API in Loopthink
The API's own key or service user, read-only where the vendor allows it.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which orders in the shop system are still unshipped after three days?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
Collect the API's base URL and its OpenAPI spec, or the documentation of the endpoints your team needs.
2
In the system itself, create an API key or service user with the fewest rights that still read what you need. If the vendor has no read-only option, the roles in Loopthink are what limits it.
3
Paste URL, spec and key into Loopthink. Name the tools in your own business language and mark the personal fields; that is configuration, not code.
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: Loopthink pricing: what Team includes · MCP specification · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Use cases

What people actually ask Claude about Any REST API.

Operations
“Which orders in the shop system are still unshipped after three days?”
Support
“Show me the last five tickets from customer 4711 in the helpdesk.”
Management
“How many new contracts did the CRM record this month, by region?”

Why Loopthink

Why not build the MCP server yourself?

Your shop system, helpdesk, ERP module or vendor API has no MCP server. Building one takes an engineer days and leaves one token in a config file that everyone copies.

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

Tool	Operations	Support	Management
List & filter records	Operations may use List & filter records	Support may use List & filter records	Management may use List & filter records
Get one record	Operations may use Get one record	Support may use Get one record	Management may not use Get one record
Reports & aggregates	Operations may use Reports & aggregates	Support may not use Reports & aggregates	Management may use Reports & aggregates
Related records	Operations may use Related records	Support may use Related records	Management may not use Related records
Write actions off by default	Operations may not use Write actions	Support may not use Write actions	Management may not use Write actions