Loopthink
by loopthink
Overview
Loopthink is a control plane for the tools you give Claude. Connect a system once — PostgreSQL, SQL Server, HubSpot, Salesforce, DynamoDB or any REST API — curate the exact operations you want exposed, and grant them to the people who should have them. Claude sees one connector; behind it sits everything your workspace has approved for you. Curated tools, not raw access. A tool is a named operation with typed parameters — "find customer by email", not a SQL console. Author them yourself, or generate them in bulk from an OpenAPI spec and keep only what belongs. Entitlements that hold. Claude lists only the servers your member group was granted, and optionally only a subset of their tools. There is no administrator bypass: a workspace owner without a grant sees nothing. Revoked access takes effect within one token lifetime. Masking before the model. Field-level rules — mask, pseudonymize or remove — run on the server, before any result is returned. A value covered by a rule never reaches Claude, and no prompt can talk around it. Read-only by default. A tool performs writes only when an administrator enables them explicitly, and read and write operations are always separate tools. EU-hosted control plane. Configuration, tool catalog and permissions are operated in the EU. You sign in with OAuth 2.0 and pick a workspace. No API keys are shared with Claude, and tokens re-validate your permissions on every refresh, so a membership change reaches the connector on its own. Requires a Loopthink account and a workspace where an administrator has granted your group at least one server.





